Management based on computer dynamically adjusted discrete phases of event correlation

ABSTRACT

Management of a customer&#39;s IT environment is facilitated by correlating events that occur within the environment, obtaining information relating to those events, and performing actions, such as environment tuning or recovery actions, based on the information. Discrete phases of processing are used to obtain the information and/or perform the actions. One or more of these discrete processing phases have tunable time intervals associated therewith. That is, at least one time interval is dynamically adjusted based on the runtime state of the environment.

TECHNICAL FIELD

This invention relates, in general, to managing customer environments toprovide support for business resiliency, and in particular, todynamically adjusting discrete phases of event correlation to obtainevent related information used in facilitating management of theenvironment.

BACKGROUND OF THE INVENTION

Today, customers attempt to manually manage and align their availabilitymanagement with their information technology (IT) infrastructure.Changes in either business needs or the underlying infrastructure areoften not captured in a timely manner and require considerable rework,leading to an inflexible environment.

Often high availability solutions and disaster recovery technologies arehandled via a number of disparate point products that target specificscopes of failure, platforms or applications. Integrating thesesolutions into an end-to-end solution is a complex task left to thecustomer, with results being either proprietary and very specific, orunsuccessful.

Customers do not have the tools and infrastructure in place to customizetheir availability management infrastructure to respond to failures in away that allows for a more graceful degradation of their environments.As a result, more drastic and costly actions may be taken (such as asite switch) when other options (such as disabling a set of applicationsor users) could have been offered, depending on business needs.

Coordination across availability management and other systems managementdisciplines is either nonexistent or accomplished via non-reusable,proprietary, custom technology.

There is little predictability as to whether the desired recoveryobjective will be achieved, prior to time of failure. There are onlymanual, labor intensive techniques to connect recovery actions with thebusiness impact of failures and degradations.

Any change in the underlying application, technologies, businessrecovery objectives, resources or their interrelationships require amanual assessment of impact to the hand-crafted recovery scheme.

SUMMARY OF THE INVENTION

Based on the foregoing, a need exists for a capability that facilitatesmanagement of an IT environment. In particular, a need exists for acapability that employs dynamically adjusted discrete phases ofprocessing to obtain a set of event related information used in managingthe environment. In one example, a time interval associated with adiscrete processing phase is dynamically adjusted based on real-timestatus of the environment, which affects the obtained set ofinformation.

The shortcomings of the prior art are overcome and additional advantagesare provided through the provision of a computer-implemented method tofacilitate event correlation. The method includes, for instance,executing a plurality of discrete phases of processing, in response toan occurrence of an event in an Information Technology (IT) environment,to obtain a set of related information associated with the event; andadjusting a time interval associated with at least one discrete phase ofthe plurality of discrete phases based on real-time status of the ITenvironment, said adjusting affecting the obtained set of relatedinformation.

Computer program products and systems relating to one or more aspects ofthe present invention are also described and claimed herein.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more aspects of the present invention are particularly pointedout and distinctly claimed as examples in the claims at the conclusionof the specification. The foregoing and other objects, features, andadvantages of the invention are apparent from the following detaileddescription taken in conjunction with the accompanying drawings inwhich:

FIG. 1 depicts one embodiment of a processing environment to incorporateand use one or more aspects of the present invention;

FIG. 2 depicts another embodiment of a processing environment toincorporate and use one or more aspects of the present invention;

FIG. 3 depicts yet a further embodiment of a processing environment toincorporate and use one or more aspects of the present invention;

FIG. 4 depicts one embodiment of a Business Resilience System used inaccordance with an aspect of the present invention;

FIG. 5A depicts one example of a screen display of a business resilienceperspective, in accordance with an aspect of the present invention;

FIG. 5B depicts one example of a screen display of a Recovery Segment,in accordance with an aspect of the present invention;

FIG. 6A depicts one example of a notification view indicating aplurality of notifications, in accordance with an aspect of the presentinvention;

FIG. 6B depicts one example of a notification message sent to a user, inaccordance with an aspect of the present invention;

FIG. 7 depicts one example of a Recovery Segment of the BusinessResilience System of FIG. 4, in accordance with an aspect of the presentinvention;

FIG. 8A depicts examples of key Recovery Time Objective properties for aparticular resource, in accordance with an aspect of the presentinvention;

FIG. 8B depicts one example in which Recovery Time Objective propertiescollectively form an observation of a Pattern System Environment, inaccordance with an aspect of the present invention;

FIG. 9 depicts one example of a Containment Region and related datastructures, in accordance with an aspect of the present invention;

FIG. 10A depicts one example of a sliding window timeline used inaccordance with an aspect of the present invention;

FIG. 10B depicts another example of the timeline depicting deltaincrements, in accordance with an aspect of the present invention;

FIGS. 11A-11E depict one embodiment of the logic to calculate aninterval window, in accordance with an aspect of the present invention;

FIG. 12 depicts one embodiment of the logic associated with processing anew Containment Region, in accordance with an aspect of the presentinvention;

FIGS. 13A-13C depict one embodiment of the logic used for customermodification of timings, in accordance with an aspect of the presentinvention;

FIGS. 14A-14J depict one embodiment of the logic for asynchronous querybuild processing used in accordance with an aspect of the presentinvention;

FIG. 15 depicts one embodiment of the logic for close sliding windowprocessing used in accordance with an aspect of the present invention;and

FIG. 16 depicts one embodiment of a computer program productincorporating one or more aspects of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

In managing a customer's environment, such as its business environment,there is a set of requirements unaddressed by existing technology, whichcauses unpredictable down time, large impact failures and recoveries,and significant extra labor cost, with resulting loss of businessrevenue. These requirements include, for instance:

-   -   1. Ensuring that there is a consistent recovery scheme across        the environment, linked to the business application, across the        different types of resources; not a different methodology        performed by platform silo. The recovery is to match the scope        of the business application, not limited in scope to a single        platform. The recovery is to be end-to-end and allow for        interaction across multiple vendor products. In one example, a        business application is defined as a process that is supported        by IT services. It is supportive of the products and/or services        created by a customer. It can be of fine granularity (e.g., a        specific service/product provided) or of coarse granularity        (e.g., a group of services/products provided).    -   2. Ability to group together mixed resource types (servers,        storage, applications, subsystems, network, etc.) into logical        groupings aligned with business processes requirements for        availability.    -   3. Ability to share resources across logical groups of        resources; ability to nest these logical group definitions, with        specifications for goal policy accepted and implemented at each        level.    -   4. Pre-specified recommendations for resource groupings, with        customization possible, and pattern matching customer        configuration with vendor or customer provided        groupings/relationships—to avoid requiring customers to start        from scratch for definitions.    -   5. Ability to group together redundant resources with functional        equivalence—use during validation when customer has less        redundancy than required to meet the Recovery Time Objective        (RTO) goal; in recovery to select an alternate resource for one        that has failed.    -   6. Ability to configure the definition of what constitutes        available, degraded, or unavailable based on customer's own        sensitivity for a given grouping of resources, and business        needs, and further aggregate the state across various resources        to produce an overall state for the business application. The        state is to be assessed real time, based on what is actually        occurring in the system at the time, rather than fixed        definitions. In some cases, a performance slowdown might flag a        degraded environment, and in other cases, a failure may be        necessary before flagging a degraded or unavailable environment.        The definitions of available, degraded and unavailable are to be        consumed by an availability system that evaluates them in the        context of a policy, and then determines appropriate action,        including possibly launching recovery automatically.    -   7. Ability to relate the redundancy capability of relevant        resources to the availability status of a business application.    -   8. Allow customers to configure when recovery actions can be        delegated to lower level resources, particularly since resource        sharing is becoming more relevant in many customer environments.    -   9. Include customer or vendor best practices for availability as        prespecified workflows, expressed in a standards based manner,        that can be customized.    -   10. Ability to specify quantitative business goals for the        recovery of logical groupings of resources, effecting both how        the resources are pre-configured for recovery, as well as        recovered during errors. One such quantitative goal is Recovery        Time Objective (RTO). As part of the specification of        quantitative business goals, to be able to include time bias of        applications, and facilitate the encoding of appropriate        regulatory requirements for handling of certain workloads during        changing business cycles in selected businesses, such as        financial services.    -   11. Decomposition of the overall quantified RTO goal to nested        logical groups; processing for shared groups having different        goals.    -   12. Ability to configure redundancy groupings and co-location        requirements with resources from other vendors, using a        representation for resources (which may be, for example,        standards based), with ability to clearly identify the vendor as        part of the resource definition.    -   13. Ability to use customer's own historical system measures to        automatically generate various system environments, then use        these system environments when specifying quantitative recovery        goals (since recovery time achievability and requirements are        not consistent across time of day, business cycle, etc.). The        function is to be able to incorporate historical information        from dependent resources, as part of the automatic generation of        system environments.    -   14. Specification of statistical thresholds for acceptability of        using historical information; customer specification directly of        expected operation times and directive to use customer specified        values.    -   15. Environments are matched to IT operations and time of day,        with automatic processing under a new system environment at time        boundaries—no automatic internal adjustment of RTO is to be        allowed, rather changed if the customer has specified that a        different RTO is needed for different system environments.    -   16. Goal Validation—Prior to failure time. Ability to see        assessment of achievable recovery time, in, for instance, a        Gantt chart like manner, detailing what is achievable for each        resource and taking into account overlaps of recovery sequences,        and differentiating by system environment. Specific use can be        during risk assessments, management requests for additional        recovery related resources, mitigation plans for where there are        potentials for RTO miss. Example customer questions:        -   1 What is my expected recovery time for a given application            during “end of month close” system environment?        -   What is the longest component of that recovery time?        -   Can I expect to achieve the desired RTO during the “market            open” for stock exchange or financial services applications?        -   What would be the optimal sequence and parallelization of            recovery for the resources used by my business application?    -   17. Ability to prepare the environment to meet the desired        quantitative business goals, allowing for tradeoffs when shared        resources are involved. Ensure that both automated and        non-automated tasks can be incorporated into the        pre-conditioning. Example of customer question: What would I        need to do for pre-conditioning my system to support the RTO        goal I need to achieve for this business application?    -   18. Ability to incorporate operations from any vendors'        resources for pre-conditioning or recovery workflows, including        specification of which pre-conditioning operations have effect        on recoveries, which operations have dependencies on others,        either within vendor resources or across resources from multiple        vendors.    -   19. Customer ability to modify pre-conditioning workflows,        consistent with supported operations on resources.    -   20. Ability to undo pre-conditioning actions taken, when there        is a failure to complete a transactionally consistent set of        pre-conditioning actions; recognize the failure, show customers        the optional workflow to undo the actions taken, allow them to        decide preferred technique for reacting to the failure—manual        intervention, running undo set of operations, combination of        both, etc.    -   21. Ability to divide pre-conditioning work between long running        and immediate, nondisruptive short term actions.    -   22. Impact only the smallest set of resources required during        recovery, to avoid negative residual or side effects for        attempting to recover a broader set of resources than what is        actually impacted by the failure.    -   23. Choosing recovery operations based on determination of which        recovery actions address the minimal impact, to meet goal, and        then prepare for subsequent escalation in event of failure of        initial recovery actions.    -   24. Choosing a target for applications and operating systems        (OS), based on customer co-location specifications, redundancy        groups, and realtime system state.    -   25. Ability for customer to indicate specific effect that        recovery of a given business process can have on another        business process—to avoid situations where lower priority        workloads are recovered causing disruption to higher priority        workloads; handling situations where resources are shared.    -   26. Ability to prioritize ongoing recovery processing over        configuration changes to an availability system, and over any        other administration functions required for the availability        system.    -   27. Ability for recoveries and pre-conditioning actions to run        as entire transactions so that partial results are appropriately        accounted for and backed out or compensated, based on actual        effect (e.g., during recovery time or even pre-conditioning, not        all actions may succeed, so need to preserve a consistent        environment).    -   28. Allow for possible non-responsive resources or underlying        infrastructure that does not have known maximum delays in        response time in determining recovery actions, while not going        beyond the allotted recovery time.    -   29. Allow customer to change quantified business recovery        goals/targets without disruption to the existing recovery        capability, with appropriate labeling of version of the policy        to facilitate interaction with change management systems.    -   30. Allow customers to change logical groupings of resources        that have assigned recovery goals, without disruption to the        existing recovery capability, with changes versioned to        facilitate interaction with change management systems.    -   31. Ability to specify customizable human tasks, with time        specifications that can be incorporated into the goal        achievement validation so customers can understand the full time        involved for a recovery and where focusing on IT and people time        is critical to reducing RTO.    -   32. There is a requirement/desire to implement dynamically        modified redundancy groupings for those resources which are high        volume—automatic inclusion based on a specified set of        characteristics and a matching criteria.    -   33. There is a requirement/desire to automatically add/delete        resources from the logical resource groupings for sets of        resources that are not needing individual assessment.

The above set of requirements is addressed, however, by a BusinessResiliency (BR) Management System, of which one or more aspects of thepresent invention are included. The Business Resiliency ManagementSystem provides, for instance:

-   -   1. Rapid identification of fault scope.        -   Correlation and identification of dependencies between            business functions and the supporting IT resources.        -   Impact analysis of failures affecting business functions,            across resources used within the business functions,            including the applications and data.        -   Isolation of failure scope to smallest set of resources, to            ensure that any disruptive recovery actions effect only the            necessary resources.    -   2. Rapid granular and graceful degradation of IT service.        -   Discontinuation of services based on business priorities.        -   Selection of alternate resources at various levels may            include selection of hardware, application software, data,            etc.        -   Notifications to allow applications to tailor or reduce            service consumption during times of availability            constraints.    -   3. Integration of availability management with normal business        operations and other core business processes.        -   Policy controls for availability and planned            reconfiguration, aligned with business objectives.        -   Encapsulation, integration of isolated point solutions into            availability IT fabric, through identification of affected            resources and operations initiated by the solutions, as well            as business resiliency.        -   Goal based policy support, associated with Recovery Segments            that may be overlapped or nested in scope.        -   Derivation of data currency requirements, based on business            availability goals.

One goal of the BR system is to allow customers to align theirsupporting information technology systems with their business goals forhandling failures of various scopes, and to offer a continuum ofrecovery services from finer grained process failures to broader scopedsite outages. The BR system is built around the idea of identifying thecomponents that constitute a business function, and identifyingsuccessive levels of recovery that lead to more complex constructs asthe solution evolves. The various recovery options are connected by anoverall BR management capability that is driven by policy controls.

Various characteristics of one embodiment of a BR system include:

-   -   1. Capability for dynamic generation of recovery actions, into a        programmatic and manageable entity.    -   2. Dynamic generation of configuration changes required/desired        to support a customer defined Recovery Time Objective (RTO)        goal.    -   3. Dynamic definition of key Pattern System Environments (PSEs)        through statistical analysis of historical observations.    -   4. Validation of whether requested RTO goals are achievable,        based on observed historical snapshots of outages or customer        specified recovery operation time duration, in the context of        key Pattern System Environments.    -   5. BR system dynamic, automatic generation and use of standards        based Business Process Execution Language (BPEL) workflows to        specify recovery transactions and allow for customer integration        through workflow authoring tools.    -   6. Ability to configure customized scopes of recovery, based on        topologies of resources and their relationships, called Recovery        Segments (RSs).    -   7. Best practice workflows for configuration and recovery,        including, but not limited to, those for different resource        types: servers, storage, network, and middleware, as examples.    -   8. Ability to customize the definition of available, degraded,        unavailable states for Recovery Segments.    -   9. Ability to represent customers' recommended configurations        via best practice templates.    -   10. Ability to define the impact that recovery of one business        application is allowed to have on other business applications.    -   11. Ability to correlate errors from the same or multiple        resources into related outages and perform root cause analysis        prior to initiating recovery actions.    -   12. Quantified policy driven, goal oriented management of        unplanned outages.    -   13. Groupings of IT resources that have associated, consistent        recovery policy and recovery actions, classified as Recovery        Segments.    -   14. Handling of situations where the underlying error detection        and notifications system itself is unavailable.

A Business Resilience System is capable of being incorporated in andused by many types of environments. One example of a processingenvironment to incorporate and use aspects of a BR system, including oneor more aspects of the present invention, is described with reference toFIG. 1.

Processing environment 100 includes, for instance, a central processingunit (CPU) 102 coupled to memory 104 and executing an operating system106. Examples of operating systems include AIX® and z/OS®, offered byInternational Business Machines Corporation; Linux; etc. AIX® and z/OS®are registered trademarks of International Business MachinesCorporation, Armonk, N.Y., U.S.A. Other names used herein may beregistered trademarks, trademarks or product names of InternationalBusiness Machines Corporation or other companies.

The operating system manages execution of a Business Resilience RuntimeComponent 108 of a Business Resilience System, described herein, and oneor more applications 110 of an application container 112.

As examples, processing environment 100 includes an IBM® System Z™processor or a pSeries® server offered by International BusinessMachines Corporation; a Linux server; or other servers, processors, etc.Processing environment 100 may include more, less and/or differentcomponents than described herein. (pSeries® is a registered trademark ofInternational Business Machines Corporation, Armonk, N.Y., USA.)

Another example of a processing environment to incorporate and useaspects of a BR System, including one or more aspects of the presentinvention, is described with reference to FIG. 2.

As shown, a processing environment 200 includes for instance, a centralprocessing complex 202 coupled to an input/output (I/O) subsystem 204.Central processing complex 202 includes, for instance, a centralprocessing unit 206, memory 208, an operating system 210, a databasemanagement system 212, a Business Resilience Runtime Component 214, anapplication container 216 including one or more applications 218, and anI/O facility 220.

I/O facility 220 couples central processing complex 202 to I/O subsystem204 via, for example, a dynamic switch 230. Dynamic switch 230 iscoupled to a control unit 232, which is further coupled to one or moreI/O devices 234, such as one or more direct access storage devices(DASD).

Processing environments 100 and/or 200 may include, in otherembodiments, more, less and/or different components.

In yet another embodiment, a central processing complex 300 (FIG. 3)further includes a network service 302, which is used to couple acentral processing complex 300 to a processing environment 304 via anetwork subsystem 306.

For example, network service 302 of central processing complex 300 iscoupled to a switch 308 of network subsystem 306. Switch 308 is coupledto a switch 310 via routers 312 and firewalls 314. Switch 310 is furthercoupled to a network service 316 of processing environment 304.

Processing environment 304 further includes, for instance, a centralprocessing unit 320, a memory 322, an operating system 324, and anapplication container 326 including one or more applications 328. Inother embodiments, it can include more, less and/or differentcomponents.

Moreover, CPC 300 further includes, in one embodiment, a centralprocessing unit 330, a memory 332, an operating system 334, a databasemanagement system 336, a Business Resilience Runtime Component 338, anapplication container 340 including one or more applications 342, and anI/O facility 344. It also may include more, less and/or differentcomponents.

I/O facility 344 is coupled to a dynamic switch 346 of an I/O subsystem347. Dynamic switch 346 is further coupled to a control unit 348, whichis coupled to one or more I/O devices 350.

Although examples of various environments are provided herein, these areonly examples. Many variations to the above environments are possibleand are considered within the scope of the present invention.

In the above-described environments, a Business Resilience RuntimeComponent of a Business Resilience System is included. Further detailsassociated with a Business Resilience Runtime Component and a BusinessResilience System are described with reference to FIG. 4.

In one example, a Business Resilience System 400 is a component thatrepresents the management of recovery operations and configurationsacross an IT environment. Within that Business Resilience System, thereis a Business Resilience Runtime Component (402) that represents themanagement functionality across multiple distinct Recovery Segments, andprovides the service level automation and the support of creation of therecovery sequences. In addition, there are user interface (404),administration (406), installation (408) and configuration template(410) components within the Business Resilience System that enable theadministrative operations that are to be performed. Each of thesecomponents is described in further detail below.

Business Resilience Runtime Component 402 includes a plurality ofcomponents of the BR System that are directly responsible for thecollection of observations, creation of PSEs, policy acceptance,validation, error detection, and formulation of recovery sequences. Asone example, Business Resilience Runtime Component 402 includes thefollowing components:

-   -   1. One or more Business Resilience Managers (BRM) (412).        -   The Business Resilience Manager (BRM) is the primary            component containing logic to detect potential errors in the            IT environment, perform assessment to find resources causing            errors, and formulate recovery sequences to reestablish the            desired state for resources for all Recovery Segments that            may be impacted.        -   The Business Resilience Manager is a component of which            there can be one or more. It manages a set of Recovery            Segments, and has primary responsibility to formulate            recovery sequences. The association of which Recovery            Segments are managed by a given BRM is determined at            deployment time by the customer, with the help of deployment            time templates. BRMs are primarily responsible for            operations that relate to error handling and recovery            workflow generation, and cross RS interaction.    -   2. One or more Recovery Segments (RS) (414).        -   Recovery Segments are customer-defined groupings of IT            resources to which consistent availability policy is            assigned. In other words, a Recovery Segment acts as a            context within which resource recovery is performed. In many            cases, Recovery Segments are compositions of IT resources            that constitute logical entities, such as a middleware and            its related physical resources, or an “application” and its            related components.        -   There is no presumed granularity of a Recovery Segment.            Customers can choose to specify fine-grained Recovery            Segments, such as one for a given operating system, or a            coarser grained Recovery Segment associated with a business            process and its component parts, or even a site, as            examples.        -   Relationships between IT resources associated with a RS are            those which are part of the IT topology.        -   Recovery Segments can be nested or overlapped. In case of            overlapping Recovery Segments, there can be policy            associated with each RS, and during policy validation,            conflicting definitions are reconciled. Runtime assessment            is also used for policy tradeoff.        -   The Recovery Segment has operations which support policy            expression, validation, decomposition, and assessment of            state.        -   The number of Recovery Segments supported by a BR System can            vary, depending on customer configurations and business            needs.        -   One BRM can manage multiple Recovery Segments, but a given            RS is managed by a single BRM. Further, Recovery Segments            that share resources, or are subset/superset of other            Recovery Segments are managed by the same BRM, in this            example. Multiple BRMs can exist in the environment,            depending on performance, availability, and/or            maintainability characteristics.    -   3. Pattern System Environments (PSEs) (416).        -   Pattern System Environments (PSEs) are representations of a            customer's environment. Sets of observations are clustered            together using available mathematical tooling to generate            the PSEs. In one embodiment, the generation of a PSE is            automatic. A PSE is associated with a given RS, but a PSE            may include information that crosses RSs.        -   As one example, the representation is programmatic in that            it is contained within a structure from which information            can be added/extracted.    -   4. Quantified Recovery Goal (418).        -   A quantified recovery goal, such as a Recovery Time            Objective (RTO), is specified for each Recovery Segment that            a customer creates. If customers have multiple Pattern            System Environments (PSEs), a unique RTO for each PSE            associated with the RS may be specified.    -   5. Containment Region (CR) (420).        -   Containment Region(s) are components of the BR System which            are used at runtime to reflect the scope and impact of an            outage. A Containment Region includes, for instance,            identification for a set of impacted resources, as well as            BR specific information about the failure/degraded state, as            well as proposed recovery. CRs are associated with a set of            impacted resources, and are dynamically constructed by BR in            assessing the error.        -   The original resources reporting degraded availability, as            well as the resources related to those reporting degraded            availability, are identified as part of the Containment            Region. Impacted resources are accumulated into the topology            by traversing the IT relationships and inspecting the            attributes defined to the relationships. The Containment            Region is transitioned to an inactive state after a            successful recovery workflow has completed, and after all            information (or a selected subset in another example) about            the CR has been logged.    -   6. Redundancy Groups (RG) (422).        -   Redundancy Group(s) (422) are components of the BR System            that represent sets of logically equivalent services that            can be used as alternates when a resource experiences            failure or degradation. For example, three instances of a            database may form a redundancy group, if an application            server requires connectivity to one of the set of three, but            does not specify one specific instance.        -   There can be zero or more Redundancy Groups in a BR System.        -   Redundancy Groups also have an associated state that is            maintained in realtime, and can contribute to the definition            of what constitutes available, degraded, or unavailable            states. In addition, Redundancy Groups members are            dynamically and automatically selected by the BR System,            based on availability of the member and co-location            constraints.    -   7. BR Manager Data Table (BRMD) (424).        -   BR maintains specific internal information related to            various resources it manages and each entry in the BR            specific Management Data (BRMD) table represents such a            record of management. Entries in the BRMD represent IT            resources.    -   8. BR Manager Relationship Data Table (BRRD) (426).        -   BR maintains BR specific internal information related to the            pairings of resources it needs to interact with, and each            entry in the BR specific Relationship Data (BRRD) table            represents an instance of such a pairing. The pairing record            identifies the resources that participate in the pairing,            and resources can be any of those that appear in the BRMD            above. The BRRD includes information about the pairings,            which include operation ordering across resources, failure            and degradation impact across resources, constraint            specifications for allowable recovery actions, effect an            operation has on resource state, requirements for resource            to co-locate or anti-co-locate, and effects of preparatory            actions on resources.    -   9. BR Asynchronous Distributor (BRAD) (428).        -   The BR Asynchronous Distributor (BRAD) is used to handle            asynchronous behavior during time critical queries for            resource state and key properties, recovery, and for getting            observations back from resources for the observation log.    -   10. Observation Log (430).        -   The Observation Log captures the information that is            returned through periodic observations of the environment.            The information in the Observation Log is used by cluster            tooling to generate Pattern System Environments (PSE).    -   11. RS Activity Log (432).        -   Each RS has an activity log that represents the RS actions,            successes, failures. Activity logs are internal BR            structures. Primarily, they are used for either problem            determination purposes or at runtime, recovery of failed BR            components. For example, when the RS fails and recovers, it            reads the Activity Log to understand what was in progress at            time of failure, and what needs to be handled in terms of            residuals.    -   12. BRM Activity Log (434).        -   The BRM also has an activity log that represents BRM            actions, success, failures. Activity logs are internal BR            structures.    -   13. Transaction Table (TT) (436).        -   The transaction table is a serialization mechanism used to            house the counts of ongoing recovery and preparatory            operations. It is associated with the RS, and is referred to            as the RS TT.

In addition to the Business Resilience Runtime Component of the BRsystem, the BR system includes the following components, previouslymentioned above.

User Interface (UI) Component (404).

-   -   The User interface component is, for instance, a graphical        environment through which the customer's IT staff can make        changes to the BR configuration. As examples: create and manage        Recovery Segments; specify recovery goals; validate        achievability of goals prior to failure time; view and alter BR        generated workflows.    -   The user interface (UI) is used as the primary interface for        configuring BR. It targets roles normally associated with a        Business Analyst, Solution Architect, System Architect, or        Enterprise Architect, as examples.    -   One purpose of the BR UI is to configure the BR resources. It        allows the user to create BR artifacts that are used for a        working BR runtime and also monitors the behaviors and        notifications of these BR resources as they run. In addition,        the BR UI allows interaction with resources in the environment        through, for instance, relationships and their surfaced        properties and operations. The user can add resources to BR to        affect recovery and behaviors of the runtime environment.    -   The BR UI also surfaces recommendations and best practices in        the form of templates. These are reusable constructs that        present a best practice to the user which can then be approved        and realized by the user.    -   Interaction with the BR UI is based on the typical editor save        lifecycle used within, for instance, the developmental tool        known as Eclipse (available and described at www.Eclipse.org).        The user typically opens or edits an existing resource, makes        modifications, and those modifications are not persisted back to        the resource until the user saves the editor.    -   Predefined window layouts in Eclipse are called perspectives.        Eclipse views and editors are displayed in accordance with the        perspective's layout, which can be customized by the user. The        BR UI provides a layout as exemplified in the screen display        depicted in FIG. 5A.    -   Screen display 500 depicted in FIG. 5A displays one example of a        Business Resilience Perspective. Starting in the upper left        corner and rotating clockwise, the user interface includes, for        instance:        -   1. Business Resilience View 502        -   This is where the user launches topologies and definition            templates for viewing and editing.        -   2. Topology/Definition Template Editor 504        -   This is where the editors are launched from the Business            Resilience View display. The user can have any number of            editors open at one time.        -   3. Properties View/Topology Resources View/Search View 506        -   The property and topology resource views are driven off the            active editor. They display information on the currently            selected resource and allow the user to modify settings            within the editor.        -   4. Outline View 508        -   This view provides a small thumbnail of the topology or            template being displayed in the editor. The user can pan            around the editor quickly by moving the thumbnail.    -   The topology is reflected by a RS, as shown in the screen        display of FIG. 5B. In FIG. 5B, a Recovery Segment 550 is        depicted, along with a list of one or more topology resources        552 of the RS (not necessarily shown in the current view of the        RS).    -   In one example, the BR UI is created on the Eclipse Rich Client        Platform (RCP), meaning it has complete control over the Eclipse        environment, window layouts, and overall behavior. This allows        BR to tailor the Eclipse platform and remove Eclipse artifacts        not directly relevant to the BR UI application, allowing the        user to remain focused, while improving usability.    -   BR extends the basic user interface of Eclipse by creating        software packages called “plugins’ that plug into the core        Eclipse platform architecture to extend its capabilities. By        implementing the UI as a set of standard Eclipse plug-ins, BR        has the flexibility to plug into Eclipse, WebSphere Integration        Developer, or Rational product installs, as examples. The UI        includes two categories of plug-ins, those that are BR specific        and those that are specific to processing resources in the IT        environment. This separation allows the resource plug-ins to be        potentially re-used by other products.    -   By building upon Eclipse, BR has the option to leverage other        tooling being developed for Eclipse. This is most apparent in        its usage of BPEL workflow tooling, but the following packages        and capabilities are also being leveraged, in one embodiment, as        well:        -   The Eclipse platform provides two graphical toolkit            packages, GEF and Draw2D, which are used by BR, in one            example, to render topology displays and handle the rather            advanced topology layouts and animations. These packages are            built into the base Eclipse platform and provide the            foundation for much of the tooling and topology user            interfaces provided by this design.        -   The Eclipse platform allows building of advanced editors and            forms, which are being leveraged for BR policy and template            editing. Much of the common support needed for editors, from            the common save lifecycle to undo and redo support, is            provided by Eclipse.        -   The Eclipse platform provides a sophisticated Welcome and            Help system, which helps introduce and helps users to get            started configuring their environment. Likewise, Eclipse            provides a pluggable capability to create task instructions,            which can be followed step-by-step by the user to accomplish            common or difficult tasks.

BR Admin Mailbox (406) (FIG. 4).

-   -   The BR Admin (or Administrative) Mailbox is a mechanism used by        various flows of the BR runtime to get requests to an        administrator to take some action. The Admin mailbox        periodically retrieves information from a table, where BR keeps        an up-to-date state.    -   As an example, the Admin Mailbox defines a mechanism where BR        can notify the user of important events needing user attention        or at least user awareness. The notifications are stored in the        BR database so they can be recorded while the UI is not running        and then shown to the user during their next session.    -   The notifications are presented to the user, in one example, in        their own Eclipse view, which is sorted by date timestamp to        bubble the most recent notifications to the top. An example of        this view is shown in FIG. 6A. As shown, a view 600 is presented        that includes messages 602 relating to resources 604. A date        timestamp 606 is also included therewith.    -   Double clicking a notification opens an editor on the        corresponding resource within the BR UI, which surfaces the        available properties and operations the user may need to handle        the notification.    -   The user is able to configure the UI to notify them whenever a        notification exceeding a certain severity is encountered. The UI        then alerts 650 the user of the notification and message when it        comes in, as shown in FIG. 6B, in one example.    -   When alerted, the user can choose to open the corresponding        resource directly. If the user selects No, the user can revisit        the message or resource by using the above notification log        view.

BR Install Logic (408) (FIG. 4).

-   -   The BR Install logic initializes the environment through        accessing the set of preconfigured template information and        vendor provided tables containing resource and relationship        information, then applying any customizations initiated by the        user.

Availability Configuration Templates (410):

-   -   Recovery Segment Templates        -   The BR System has a set of Recovery Segment templates which            represent common patterns of resources and relationships.            These are patterns matched with each individual customer            environment to produce recommendations for RS definitions to            the customer, and offer these visually for customization or            acceptance.    -   Redundancy Group Templates        -   The BR System has a set of Redundancy Group templates which            represent common patterns of forming groups of redundant            resources. These are optionally selected and pattern matched            with each individual customer environment to produce            recommendations for RG definitions to a customer.    -   BR Manager Deployment Templates        -   The BR System has a set of BR Manager Deployment templates            which represent recommended configurations for deploying the            BR Manager, its related Recovery Segments, and the related            BR management components. There are choices for distribution            or consolidation of these components. Best practice            information is combined with optimal availability and            performance characteristics to recommend a configuration,            which can then be subsequently accepted or altered by the            customer.    -   Pairing Templates        -   The BR System has a set of Pairing Templates used to            represent best practice information about which resources            are related to each other.

The user interface, admin mailbox, install logic and/or templatecomponents can be part of the same computing unit executing BR Runtimeor executed on one or more other distributed computing units.

To further understand the use of some of the above components and theirinterrelationships, the following example is offered. This example isonly offered for clarification purposes and is not meant to be limitingin any way.

Referring to FIG. 7, a Recovery Segment RS 700 is depicted. It isassumed for this Recovery Segment that:

-   -   The Recovery Segment RS has been defined associated with an        instantiated and deployed BR Manager for monitoring and        management.    -   Relationships have been established between the Recovery Segment        RS and the constituent resources 702 a-702 m.    -   A goal policy has been defined and validated for the Recovery        Segment through interactions with the BR UI.    -   The following impact pairings have been assigned to the        resources and relationships:

Rule Resource #1 State Resource #2 State 1 App-A Degraded RS Degraded 2App-A Unavailable RS Unavailable 3 DB2 Degraded CICS Unavailable 4 CICSUnavailable App-A Unavailable 5 CICS Degraded App-A Degraded 6OSStorage-1 Unavailable CICS Degraded 7 OSStorage-1 Unavailable StorageCopy Set Degraded 8 DB2 User & Log Data Degraded DB2 Degraded 9OSStorage-2 Unavailable DB2 User & Log Data Degraded 10 z/OS UnavailableCICS Unavailable 11 z/OS Unavailable DB2 Unavailable 12 Storage Copy SetDegraded CICS User & Log Data Degraded 13 Storage Copy Set Degraded DB2User & Log Data Degraded

-   -   The rules in the above table correspond to the numbers in the        figure. For instance, #12 (704) corresponds to Rule 12 above.    -   Observation mode for the resources in the Recovery Segment has        been initiated either by the customer or as a result of policy        validation.    -   The environment has been prepared as a result of that goal        policy via policy validation and the possible creation and        execution of a preparatory workflow.    -   The goal policy has been activated for monitoring by BR.

As a result of these conditions leading up to runtime, the followingsubscriptions have already taken place:

-   -   The BRM has subscribed to runtime state change events for the        RS.    -   RS has subscribed to state change events for the constituent        resources.

These steps highlight one example of an error detection process:

-   -   The OSStorage-1 resource 702 h fails (goes Unavailable).    -   RS gets notified of state change event.    -   1^(st) level state aggregation determines:        -   Storage Copy Set→Degraded        -   CICS User & Log Data→Degraded        -   DB2 User & Log Data→Degraded        -   DB2→Degraded        -   CICS→Unavailable        -   App-A→Unavailable    -   1^(st) level state aggregation determines:        -   RS→Unavailable    -   BRM gets notified of RS state change. Creates the following        Containment Region:

Resource Reason OSStorage-1 Unavailable Storage Copy Set Degraded CICSUser & Log Data Degraded DB2 User & Log Data Degraded DB2 Degraded App-AUnavailable CICS Unavailable RS Unavailable

-   -   Creates a recovery workflow based on the following resources:

Resource State OSStorage-1 Unavailable Storage Copy Set Degraded CICSUser & Log Data Degraded DB2 User & Log Data Degraded DB2 Degraded App-AUnavailable CICS Unavailable RS Unavailable

In addition to the above, BR includes a set of design points that helpin the understanding of the system. These design points include, forinstance:

Goal Policy Support

BR is targeted towards goal based policies—the customer configures histarget availability goal, and BR determines the preparatory actions andrecovery actions to achieve that goal (e.g., automatically).

Availability management of the IT infrastructure through goal basedpolicy is introduced by this design. The BR system includes the abilityto author and associate goal based availability policy with the resourceRecovery Segments described herein. In addition, support is provided todecompose the goal policy into configuration settings, preparatoryactions and runtime procedures in order to execute against the deployedavailability goal. In one implementation of the BR system, the RecoveryTime Objective (RTO—time to recover post outage) is a supported goalpolicy. Additional goal policies of data currency (e.g., Recovery PointObjective) and downtime maximums, as well as others, can also beimplemented with the BR system. Recovery Segments provide the contextfor association of goal based availability policies, and are the scopefor goal policy expression supported in the BR design. The BR systemmanages the RTO through an understanding of historical information,metrics, recovery time formulas (if available), and actions that affectthe recovery time for IT resources.

RTO goals are specified by the customer at a Recovery Segment level andapportioned to the various component resources grouped within the RS. Inone example, RTO goals are expressed as units of time intervals, such asseconds, minutes, and hours. Each RS can have one RTO goal per PatternSystem Environment associated with the RS. Based on the metricsavailable from the IT resources, and based on observed history and/ordata from the customer, the RTO goal associated with the RS is evaluatedfor achievability, taking into account which resources are able to berecovered in parallel.

Based on the RTO for the RS, a set of preparatory actions expressed as aworkflow is generated. This preparatory workflow configures theenvironment or makes alterations in the current configuration, toachieve the RTO goal or to attempt to achieve the goal.

In terms of optimizing RTO, there are tradeoffs associated with thechoices that are possible for preparatory and recovery actions.Optimization of recovery choice is performed by BR, and may includeinteraction at various levels of sophistication with IT resources. Insome cases, BR may set specific configuration parameters that aresurfaced by the IT resource to align with the stated RTO. In othercases, BR may request that an IT resource itself alter its managementfunctions to achieve some portion of the overall RS RTO. In either case,BR aligns availability management of the IT resources contained in theRS with the stated RTO.

Metrics and Goal Association

In this design, as one example, there is an approach to collecting therequired or desired metrics data, both observed and key varying factors,system profile information that is slow or non-moving, as well aspotential formulas that reflect a specific resource's use of the keyfactors in assessing and performing recovery and preparatory actions,historical data and system information. The information and raw metricsthat BR uses to perform analysis and RTO projections are expressed aspart of the IT resources, as resource properties. BR specificinterpretations and results of statistical analysis of key factorscorrelated to recovery time are kept as BR Specific Management data(BRMD).

Relationships Used By BR, and BR Specific Resource Pairing Information

BR maintains specific information about the BR management of eachresource pairing or relationship between resources. Informationregarding the BR specific data for a resource pairing is kept by BR,including information such as ordering of operations across resources,impact assessment information, operation effect on availability state,constraint analysis of actions to be performed, effects of preparatoryactions on resources, and requirements for resources to co-locate oranti-co-locate.

Evaluation of Failure Scope

One feature of the BR function is the ability to identify the scope andimpact of a failure. The BR design uses a Containment Region to identifythe resources affected by an incident. The Containment Region isinitially formed with a fairly tight restriction on the scope of impact,but is expanded on receiving errors related to the first incident. Theimpact and scope of the failure is evaluated by traversing the resourcerelationships, evaluating information on BR specific resource pairinginformation, and determining most current state of the resourcesimpacted.

Generation and Use of Workflow

Various types of preparatory and recovery processes are formulated andin some cases, optionally initiated. Workflows used by BR aredynamically generated based on, for instance, customer requirements forRTO goal, based on actual scope of failure, and based on anyconfiguration settings customers have set for the BR system.

A workflow includes one or more operations to be performed, such asStart CICS, etc. Each operation takes time to execute and this amount oftime is learned based on execution of the workflows, based on historicaldata in the observation log or from customer specification of executiontime for operations. The workflows formalize, in a machine readable,machine editable form, the operations to be performed.

In one example, the processes are generated into Business ProcessExecution Language (BPEL) compliant workflows with activities that areoperations on IT resources or specified manual, human activities. Forexample, BRM automatically generates the workflows in BPEL. Thisautomatic generation includes invoking routines to insert activities tobuild the workflow, or forming the activities and building the XML(Extensible Mark-Up Language). Since these workflows are BPEL standardcompliant, they can be integrated with other BPEL defined workflowswhich may incorporate manual activities performed by the operationsstaff. These BR related workflows are categorized as follows, in oneexample:

-   -   Preparatory—Steps taken during the policy prepare phase in        support of a given goal, such as the setting of specific        configuration values, or the propagation of availability related        policy on finer grained resources in the Recovery Segment        composition. BR generates preparatory workflows, for instance,        dynamically. Examples of preparatory actions include setting up        storage replication, and starting additional instances of        middleware subsystems to support redundancy.    -   Recovery—Steps taken as a result of fault detection during        runtime monitoring of the environment, such as, for example,        restarting a failed operating system (OS). BR generates recovery        workflows dynamically, in one example, based on the actual        failure rather than a prespecified sequence.    -   Preventive—Steps taken to contain or fence an error condition        and prevent the situation from escalating to a more substantial        outage or impact; for example, the severing of a failed        resource's relationship instances to other resources. Preventive        workflows are also dynamically generated, in one example.    -   Return—Steps taken to restore the environment back to ‘normal        operations’ post recovery, also represented as dynamically        generated workflows, as one example.

Capturing of Workflow Information

Since the set of BR actions described above modify existing ITenvironments, visibility to the actions that are taken by BR prior tothe actual execution is provided. To gain trust in the decisions andrecommendations produced by BR, the BR System can run in ‘advisorymode’. As part of advisory mode, the possible actions that would betaken are constructed into a workflow, similar to what would be done toactually execute the processes. The workflows are then made visiblethrough standard workflow authoring tooling for customers to inspect ormodify. Examples of BPEL tooling include:

-   -   Bolie, et al., BPEL Cookbook: Best Practices for SOA-based        Integration and Composite Applications Development, ISBN        1904811337, 2006, PACKT Publishing, hereby incorporated herein        by reference in its entirety;    -   Juric, et al., Business Process Execution Language for Web        Services: BPEL and BPEL YWS, ISBN 1-904811-18-3, 2004, PACKT        Publishing, hereby incorporated herein by reference in its        entirety.    -   http://www-306.ibm.com/software/integration/wid/about/?S_CMP=rnav    -   http://www.eclipse.org/bpel/    -   http://www.parasoft.com/jsp/products/home.jsp;jessionid=aaa56iqFywA-HJ?product=BPEL&redname=googbpelm&referred=searchengine%2Fgoogle%Fbpel

Tooling Lifecycle, Support of Managed Resources and Roles

BR tooling spans the availability management lifecycle from definitionof business objectives, IT resource selection, availability policyauthoring and deployment, development and deployment of runtimemonitors, etc. In one example, support for the following is captured inthe tooling environment for the BR system:

-   -   Visual presentation of the IT resources & their relationships,        within both an operations and administration context.    -   Configuration and deployment of Recovery Segments and BRMs.    -   Authoring and deployment of a BR policy.    -   Modification of availability configuration or policy changes for        BR.    -   BPEL tooling to support viewing of BR created, as well as        customer authored, workflows.    -   BPEL tooling to support monitoring of workflow status, related        to an operations console view of IT resource operational state.

Policy Lifecycle

The policy lifecycle for BR goal policies, such as RTO goals, includes,for example:

-   -   Define—Policy is specified to a RS, but no action is taken by        the BRM to support the policy (observation information may be        obtained).    -   Validate—Policy is validated for syntax, capability, etc.;        preparatory workflow created for viewing and validation by        customer.    -   Prepare—Preparatory action workflows are optionally executed.    -   Activate—Policy is activated for runtime monitoring of the        environment.    -   Modify—Policy is changed dynamically in runtime.

Configurable State Aggregation

One of the points in determining operational state of a Recovery Segmentis that this design allows for customers to configure a definition ofspecific ‘aggregated’ states, using properties of individual ITresources. A Recovery Segment is an availability management context, inone example, which may include a diverse set of IT resources.

The customer may provide the rules logic used within the RecoverySegment to consume the relevant IT resource properties and determine theoverall state of the RS (available, degraded and unavailable, etc). Thecustomer can develop and deploy these rules as part of the RecoverySegment availability policy. For example, if there is a databaseincluded in the Recovery Segment, along with the supporting operatingsystem, storage, and network resources, a customer may configure one setof rules that requires that the database must have completed therecovery of in-flight work in order to consider the overall RecoverySegment available. As another example, customers may choose to configurea definition of availability based on transaction rate metrics for adatabase, so that if the rate falls below some value, the RS isconsidered unavailable or degraded, and evaluation of ‘failure’ impactwill be triggered within the BR system. Using these configurations,customers can tailor both the definitions of availability, as well asthe rapidity with which problems are detected, since any IT resourceproperty can be used as input to the aggregation, not just theoperational state of IT resources.

Failure During Workflow Sequences of Preparatory, Recovery, Preventive

Failures occurring during sequences of operations executed within a BPELcompliant process workflow are intended to be handled through use ofBPEL declared compensation actions, associated with the workflowactivities that took a failure. The BR System creates associated “undo”workflows that are then submitted to compensate, and reset theenvironment to a stable state, based on where in the workflow thefailure occurred.

Customer Values

The following set of customer values, as examples, are derived from theBR system functions described above, listed here with supportingtechnologies from the BR system:

-   -   Align total IT runtime environment to business function        availability objectives:        -   RS definition from representation of IT Resources;        -   Goal (RTO) and action policy specification, validation and            activation; and        -   Tooling by Eclipse, as an example, to integrate with IT            process management.    -   Rapid, flexible, administrative level:        -   Alteration of operation escalation rules;        -   Customization of workflows for preparatory and recovery to            customer goals;        -   Customization of IT resource selection from RG based on            quality of service (QoS);        -   Alteration of definition of IT resource and business            application state (available, degraded, or unavailable);        -   Customization of aggregated state;        -   Modification of topology for RS and RG definition;        -   Selection of BR deployment configuration;        -   Alteration of IT resource recovery metrics;        -   Customization of generated Pattern System Environments; and        -   Specification of statistical tolerances required for system            environment formation or recovery metric usage.    -   Extensible framework for customer and vendor resources:        -   IT resource definitions not specific to BR System; and        -   Industry standard specification of workflows, using, for            instance, BPEL standards.    -   Adaptive to configuration changes and optimization:        -   IT resource lifecycle and relationships dynamically            maintained;        -   System event infrastructure utilized for linkage of IT            resource and BR management;        -   IT resource recovery metrics identified and collected;        -   IT resource recovery metrics used in forming Pattern System            Environments;        -   Learned recovery process effectiveness applied to successive            recovery events;        -   System provided measurement of eventing infrastructure            timing;        -   Dynamic formation of time intervals for aggregation of            related availability events to a root cause; and        -   Distribution of achieved recovery time over constituent            resources.    -   Incremental adoption and coexistence with other availability        offerings:        -   Potential conflict of multiple managers for a resource based            on IT representation;        -   Workflows for recovery and preparatory reflect operations            with meta data linked to existing operations;        -   Advisory mode execution for preparatory and recovery            workflows; and        -   Incremental inclusion of resources of multiple types.    -   Support for resource sharing:        -   Overlapping and contained RS;        -   Merger of CR across RS and escalation of failure scope; and        -   Preparatory and recovery workflows built to stringency            requirements over multiple RS.    -   Extensible formalization of best practices based on industry        standards:        -   Templates and patterns for RS and RG definition;        -   Preparatory and recovery workflows (e.g., BPEL) for            customization, adoption; and        -   Industry standard workflow specifications enabling            integration across customer and multiple vendors.    -   Integration of business resilience with normal runtime        operations and IT process automation:        -   Option to base on IT system wide, open industry standard            representation of resources;        -   BR infrastructure used for localized recovery within a            system, cluster and across sites; and        -   Utilization of common system infrastructure for events,            resource discovery, workflow processing, visualization.

Management of the IT environment is adaptively performed, as describedherein and in a U.S. patent application “Adaptive Business ResiliencyComputer System for Information Technology Environments,”(POU920070364US1), Bobak et al., co-filed herewith, which is herebyincorporated herein by reference in its entirety.

Many different sequences of activities can be undertaken in creating aBR environment. The following represents one possible sequence; however,many other sequences are possible. This sequence is provided merely tofacilitate an understanding of a BR system and one or more aspects ofthe present invention. This sequence is not meant to be limiting in anyway. In the following description, reference is made to various U.S.patent applications, which are co-filed herewith.

On receiving the BR and related product offerings, an installationprocess is undertaken. Subsequent to installation of the products, a BRadministrator may define the configuration for BR manager instances withthe aid of BRM configuration templates.

Having defined the BRM configuration a next step could be to defineRecovery Segments as described in “Recovery Segments for ComputerBusiness Applications,” (POU920070108US1), Bobak et al., which is herebyincorporated herein by reference in its entirety.

Definition of a RS may use a representation of resources in a topologygraph as described in “Use of Graphs in Managing ComputingEnvironments,” (POU920070112US1), Bobak et al., which is herebyincorporated herein by reference in its entirety.

It is expected that customers will enable BR operation in “observation”mode for a period of time to gather information regarding key metricsand operation execution duration associated with resources in a RS.

At some point, sufficient observation data will have been gathered or acustomer may have sufficient knowledge of the environment to be managedby BR. A series of activities may then be undertaken to prepare the RSfor availability management by BR. As one example, the following stepsmay be performed iteratively.

A set of functionally equivalent resources may be defined as describedin “Use of Redundancy Groups in Runtime Computer Management of BusinessApplications,” (POU920070113US1), Bobak et al., which is herebyincorporated herein by reference in its entirety.

Specification of the availability state for individual resources,redundancy groups and Recovery Segments may be performed as described in“Use of Multi-Level State Assessment in Computer Business Environments,”(POU920070114US1), Bobak et al., which is hereby incorporated herein byreference in its entirety.

Representations for the IT environment in which BR is to operate may becreated from historical information captured during observation mode, asdescribed in “Computer Pattern System Environment Supporting BusinessResiliency,” (POU920070107US1), Bobak et al., which is herebyincorporated herein by reference in its entirety. These definitionsprovide the context for understanding how long it takes to performoperations which change the configuration—especially during recoveryperiods.

Information on relationships between resources may be specified based onrecommended best practices—expressed in templates—or based on customerknowledge of their IT environment as described in “Conditional ComputerRuntime Control of an Information Technology Environment Based onPairing Constructs,” (POU920070110US1), Bobak et al., which is herebyincorporated herein by reference in its entirety. Pairing processingprovides the mechanism for reflecting required or desired order ofexecution for operations, the impact of state change for one resource onanother, the effect execution of an operation is expected to have on aresource state, desire to have one subsystem located on the same systemas another and the effect an operation has on preparing the environmentfor availability management.

With preliminary definitions in place, a next activity of the BRadministrator might be to define the goals for availability of thebusiness application represented by a Recovery Segment as described in“Programmatic Validation in an Information Technology Environment,”(POU920070111US1), Bobak et al, which is hereby incorporated herein byreference in its entirety.

Managing the IT environment to meet availability goals includes havingthe BR system prioritize internal operations. The mechanism utilized toachieve the prioritization is described in “Serialization in ComputerManagement,” (POU920070105US1), Bobak et al., which is herebyincorporated herein by reference in its entirety.

Multiple operations are performed to prepare an IT environment to meet abusiness application's availability goal or to perform recovery when afailure occurs. The BR system creates workflows to achieve the requiredor desired ordering of operations, as described in “Dynamic Generationof Processes in Computing Environments,” (POU920070123US1), Bobak etal., which is hereby incorporated herein by reference in its entirety.

A next activity in achieving a BR environment might be execution of theordered set of operations used to prepare the IT environment, asdescribed in “Dynamic Selection of Actions in an Information TechnologyEnvironment,” (POU920070117US1), Bobak et al., which is herebyincorporated herein by reference in its entirety.

Management by BR to achieve availability goals may be initiated, whichmay initiate or continue monitoring of resources to detect changes intheir operational state, as described in “Real-Time InformationTechnology Environments,” (POU920070120US1), Bobak et al., which ishereby incorporated herein by reference in its entirety. Monitoring ofresources may have already been initiated as a result of “observation”mode processing.

Changes in resource or redundancy group state may result in impactingthe availability of a business application represented by a RecoverySegment. Analysis of the environment following an error is performed.The analysis allows sufficient time for related errors to be reported,insures gathering of resource state completes in a timely manner andinsures sufficient time is provided for building and executing therecovery operations—all within the recovery time goal, as describedherein, in accordance with one or more aspects of the present invention.

A mechanism is provided for determining if events impacting theavailability of the IT environment are related, and if so, aggregatingthe failures to optimally scope the outage, as described in “Managementof Computer Events in a Computer Environment,” (POU920070118US1), Bobaket al., which is hereby incorporated herein by reference in itsentirety.

Ideally, current resource state can be gathered after scoping of afailure. However, provisions are made to insure management to theavailability goal is achievable in the presence of non-responsivecomponents in the IT environment, as described in “Managing the ComputerCollection of Information in an Information Technology Environment,”(POU920070121US1), Bobak et al., which is hereby incorporated herein byreference in its entirety.

With the outage scoped and current resource state evaluated, the BRenvironment can formulate an optimized recovery set of operations tomeet the availability goal, as described in “Defining a ComputerRecovery Process that Matches the Scope of Outage,” (POU920070124US1),Bobak et al., which is hereby incorporated herein by reference in itsentirety.

Formulation of a recovery plan is to uphold customer specificationregarding the impact recovery operations can have between differentbusiness applications, as described in “Managing Execution Within aComputing Environment,” (POU920070115US1), Bobak et al., which is herebyincorporated herein by reference in its entirety.

Varying levels of recovery capability exist with resources used tosupport a business application. Some resources possess the ability toperform detailed recovery actions while others do not. For resourcescapable of performing recovery operations, the BR system provides fordelegation of recovery if the resource is not shared by two or morebusiness applications, as described in “Conditional Actions Based onRuntime Conditions of a Computer System Environment,” (POU920070116US1),Bobak et al., which is hereby incorporated herein by reference in itsentirety.

Having evaluated the outage and formulated a set of recovery operations,the BR system resumes monitoring for subsequent changes to the ITenvironment.

In support of mainline BR system operation, there are a number ofactivities including, for instance:

-   -   Coordination for administrative task that employ multiple steps,        as described in “Adaptive Computer Sequencing of Actions,”        (POU920070106US1), Bobak et al., which is hereby incorporated        herein by reference in its entirety.    -   Use of provided templates representing best practices in        defining the BR system, as described in “Defining and Using        Templates in Configuring Information Technology Environments,”        (POU920070109US1), Bobak et al., which is hereby incorporated        herein by reference in its entirety.    -   Use of provided templates in formulation of workflows, as        described in “Using Templates in a Computing Environment,”        (POU920070126US1), Bobak et al., which is hereby incorporated        herein by reference in its entirety.    -   Making changes to the availability goals while supporting        ongoing BR operation, as described in “Non-Disruptively Changing        a Computing Environment,” (POU920070122US1), Bobak et al., which        is hereby incorporated herein by reference in its entirety.    -   Making changes to the scope of a business application or        Recovery Segment, as described in “Non-Disruptively Changing        Scope of Computer Business Applications Based on Detected        Changes in Topology,” (POU920070125US1), Bobak et al., which is        hereby incorporated herein by reference in its entirety.    -   Detecting and recovery for the BR system is performed        non-disruptively, as described in “Managing Processing of a        Computing Environment During Failures of the Environment,”        (POU920070365US1), Bobak et al., which is hereby incorporated        herein in its entirety.

In order to build a BR environment that meets recovery time objectives,IT configurations within a customer's location are to be characterizedand knowledge about the duration of execution for recovery timeoperations within those configurations is to be gained. ITconfigurations and the durations for operation execution vary by time,constituent resources, quantity and quality of application invocations,as examples. Customer environments vary widely in configuration of ITresources in support of business applications. Understanding thecustomer environment and the duration of operations within thoseenvironments aids in insuring a Recovery Time Objective is achievableand in building workflows to alter the customer configuration of ITresources in advance of a failure and/or when a failure occurs.

A characterization of IT configurations within a customer location isbuilt by having knowledge of the key recovery time characteristics forindividual resources (i.e., the resources that are part of the ITconfiguration being managed; also referred to as managed resources).Utilizing the representation for a resource, a set of key recovery timeobjective (RTO) metrics are specified by the resource owner. Duringongoing operations, the BR manager gathers values for these key RTOmetrics and gathers timings for the operations that are used to alterthe configuration. It is expected that customers will run the BRfunction in “observation” mode prior to having provided a BR policy foravailability management or other management. While executing in“observation” mode, the BR manager periodically gathers RTO metrics andoperation execution durations from resource representations. The key RTOmetrics properties, associated values and operation execution times arerecorded in an Observation log for later analysis through tooling. KeyRTO metrics and operation execution timings continue to be gatheredduring active BR policy management in order to maintain currency anditeratively refine data used to characterize customer IT configurationsand operation timings within those configurations.

Examples of RTO properties and value range information by resource typeare provided in the below table. It will be apparent to those skilled inthe art that additional, less, and/or different resource types,properties and/or value ranges may be provided.

Resource Type Property Value Range Operating System Identifier TextState Ok, stopping, planned stop, stopped, starting, error, lostmonitoring capability, unknown Memory Size Units in MB Number of systemsin sysplex, if integer applicable Last IPL time of day Units in time ofday/clock Type of last IPL Cold, warm, emergency Total Real StorageAvailable Units in MB GRS Star Mode Yes or No Complete IPL time to reachUnits of elapsed time ‘available’ Total CPU using to reach Units ofelapsed time available during IPL Total CPU delay to reach Units ofelapsed time available during IPL Total Memory using to reach Units inMB available during IPL Total Memory delay to reach Units of elapsedtime available during IPL Total i/o requests Integer value, number ofrequests Total i/o using to reach available Units of elapsed time duringIPL Total i/o delay to reach available Units of elapsed time during IPLComputer System (LPAR, Identifier Text Server, etc.) State Ok, stopping,stopped, planned down, starting, error, lost monitoring capability,unknown Type of CPU - model, type, Text value serial Number of CPUsinteger Number of shared processors integer Number of dedicatedprocessors integer Last Activate Time of Day Units in time of day/clockNetwork Components Group of Network Connections Identity OperationalState Ok, Starting, Disconnected, Stopping, Degraded, Unknown State ofeach associated Network Text Application Connection Performance Stats onloss and Complex delays Recovery Time for any Units in elapsed timeassociated application network connections Number of active applicationInteger network connections associated at time of network problemStopped Time/duration for Units in elapsed time group of connectoinsMaximum Network Recovery Units in elapsed time Time for any applicationconnection in group Maximum Number of active Integer connections at timeof network problem encountered, for any application connection in groupMaximum Number of Integer connections processed at time of networkrecovery, for the group of connections Maximum network connection Unitsin elapsed time recovery time/duration for any application connection inthe group Maximum Number of Integer connections dropped at time ofapplication network connection recovery, for any application connectionin the group Network Application Connection Identity Text State Ok,Stopping, Degraded, Error, Unknown Configuration Settings ComplexAssociated TCP/IP Parameter Text Settings Requirement Policies QoS or BRpolicies Performance Statistics, rules, Complex service class, number ofactive Network OS services State update Interval Units of elapsed timeLast restart time of day Units in time of day/clock Last RestartTime/Duration Units in elapsed time Network Recovery Time for app Unitsin elapsed time connection Number of active connections at Integer timeof network problem encountered, on a per app connection basis Number ofconnections Integer processed at time of network recovery, for the appconnection application network connection Units in elapsed time recoverytime/duration Number of connections at time of Integer applicationnetwork connection problem encountered Number of connections Integerprocessed at time of application network connection recovery Number ofconnections dropped Integer at time of application network connectionrecovery Network Host Connection Identity Text State Ok, Stopping,Degraded, Error, Unknown Configuration Settings Complex AssociatedTCP/IP Parameter Text Settings Requirement Policies QoS or BR policiesPerformance Statistics, rules, Complex service class, number of activeNetwork OS services State update Interval Units of elapsed time Lastrestart time of day Units in time of day/clock Last RestartTime/Duration Units in elapsed time Number of QoS Events, Integerindicating potential degradation Number of QoS Events handled, IntegerLast handled QoS Event Text Database Subsystem Name, identifier TextOperational State Operational, Nonoperational, starting, stopping, inrecovery, log suspended, backup initiated, restore initiated, restorecomplete, in checkpoint, checkpoint completed, applying log, backing outinflights, resolving indoubts, planned termination, lost monitoringcapability Time spent in log apply Units of elapsed time Time spentduring inflight Units of elapsed time processing Time spent duringindoubt Units of elapsed time processing Total time to restart Units ofelapsed time Checkpoint frequency Units of time Backout Duration Numberof records to read back in log during restart processing CPU Used duringRestart Units of elapsed time CPU Delay during Restart Units of elapsedtime Memory Used during Restart Units in MB Memory Delay during RestartUnits of elapsed time I/O Requests during restart Integer value ofnumber of requests I/O using during restart Units of elapsed time I/ODelay during restart Units of elapsed time Database Datasharing GroupIdentifer Text Operational State Operational, nonoperational, degraded(some subset of members non operational), lost monitoring capabilityNumber of locks in Shared Integer value Facility Time spent in lockcleanup for Elapsed time value last restart Database Identifier TextTablespace Identifier Text Transaction Region Identifier Text Name TextAssociated job name Text Maximum number of tasks/ Integer value threadsRestart type for next restart Warm, cold, emergency Forward log nameText System log name Text Operational State Operational, nonoperational,in recovery, starting, stop normal first quiesce, stop normal secondquiesce, stop normal third quiesce Time spent in log apply Units ofelapsed time Time during each recovery stage Units of elapsed time Totaltime to restart Units of elapsed time CPU Used during Restart Units ofelapsed time CPU Delay during Restart Units of elapsed time Memory Usedduring Restart Units in MB Memory Delay during Restart Units of elapsedtime I/O Requests during restart Integer value of number of requests I/Oconnect time during restart Units of elapsed time I/O Delay duringrestart Units of elapsed time System Logsize Units in MB Forward LogsizeUnits in MB Activity Keypoint frequency Integer - number of writesbefore activity checkpoint taken Average Transaction Rate for Number oftransactions per this region second, on average Transaction Group Groupname Text Transaction Region File Filename Text Region Name Text DatasetName Text Operational State Operational/enabled, nonoperational/disabledOpen status Open, closed, closing Transaction Identifier TextOperational State Running, failed, shunted, retry in progress RegionName (s) that can run this Text transaction Program Name Text LogicalReplication Group of Identity Text related datasets State Requiredcurrency characteristics Complex for datasets Required consistencyComplex characteristics for datasets Replication Group Identity StateReplication Session Identity State Established, in progress replication,replication successful complete Type of Session Flash copy, metromirror, etc. Duration of last replication Units in elapsed time Time ofDay for last replication Units in time of day/clock Amount of datareplicated at last Units in MB replication Roleset Identity Text StateCopySet Identity Text State Dataset Identity Text State Open, ClosedStorage Group Identity Text State Storage Volume Identity Text StateOnline, offline, boxed, unknown Logical Storage Subsystem Identity TextState Storage Subsystem Identity Text State Subsystem I/O Velocity -ratio of time channels are being used Replication Link (Logical)Identity Text between Logical Subsystems State Operational,nonoperational, degraded redundancy Number of configured pipes IntegerNumber of operational pipes Integer

A specific example of key RTO properties for a z/OS® image is depictedin FIG. 8A. As shown, for a z/OS® image 800, the following propertiesare identified: GRS mode 802, CLPA? (i.e., Was the link pack area pagespace initialized?) 804, I/O bytes moved 806, real memory size 808, #CPs 810, CPU speed 812, and CPU delay 814, as examples.

The z/OS® image has a set of RTO metrics associated therewith, asdescribed above. Other resources may also have its own set of metrics.An example of this is depicted in FIG. 8B, in which a Recovery Segment820 is shown that includes a plurality of resources 822 a-m, each havingits own set of metrics 824 a-m, as indicated by the shading.

Further, in one example, the RTO properties from each of the resourcesthat are part of the Recovery Segment for App A have been gathered by BRand formed into an “observation” for recording to the Observation log,as depicted at 850.

Resources have varying degrees of functionality to support RTO goalpolicy. Such capacity is evaluated by BR, and expressed in resourceproperty RTOGoalCapability in the BRMD entry for the resource. Twooptions for BR to receive information operation execution timings are:use of historical data or use of explicitly customer configured data. IfBR relies on historical data to make recovery time projections, thenbefore a statistically meaningful set of data is collected, thisresource is not capable of supporting goal policy. A mix of resourcescan appear in a given RS—some have a set of observations that allowclassification of the operation execution times, and others areexplicitly configured by the customer.

Calculation of projected recovery time can be accomplished in two ways,depending on customer choice: use of historical observations or use ofcustomers input timings. The following is an example of values for theRTOGoalCapability metadata that is found in the BRMD entry for theresource that indicates this choice:

UseHistoricalObservations The resource has a collection of statisticallymeaningful observations of recovery time, where definition of‘statistically valid’ is provided on a resource basis, as default by BR,but tailorable by customers UseCustomerInputTimings The customer canexplicitly set the operation timings for a resource

If the customer is in observation mode, then historical information iscaptured, regardless of whether the customer has indicated use ofexplicitly input timings or use of historical information.

The administrator can alter, on a resource basis, which set of timingsBR is to use. The default is to use historical observations. Inparticular, a change source of resource timing logic is provided thatalters the source that BR uses to retrieve resource timings. The twooptions for retrieving timings are from observed histories or explicitlyfrom admin defined times for operation execution. The default usesinformation from the observed histories, gathered from periodic polls.If the customer defines times explicitly, the customer can direct BR touse those times for a given resource. If activated, observation modecontinues and captures information, as well as running averages, andstandard deviations. The impact to this logic is to alter the source ofinformation for policy validation and formulation of recovery plan.

With respect to the historical observations, there may be astatistically meaningful set of observations to verify. The sample sizeshould be large enough so that a time range for each operation executioncan be calculated, with a sufficient confidence interval. The acceptablenumber of observations to qualify as statistically meaningful, and thedesired confidence interval are customer configurable using BR UI, butprovided as defaults in the BRMD entry for the resource. The defaultconfidence interval is 95%, in one example.

There are metrics from a resource that are employed by BR to enable andperform goal management. These include, for instance:

Metric Qualification Last observed recovery/restart time Inmilliseconds; or alternately specifying units to use in calculations Thekey factors and associated Captured at last observed recovery time, andcapturable values of the resource that affect at a point in time by BRrecovery time The key factors and associated Captured at last observedrecovery time, and capturable values of the resource that affect at apoint in time by BR other dependent resources' recovery times Observedtime interval from ‘start’ If there are various points in the resourcerecovery state to each ‘non-blocking’ state lifecycle at which itbecomes non-blocking to other resources which depend upon it, then:Observed time interval from ‘start’ state to each ‘non-blocking’ stateResource Consumption Information If the resource can provide informationabout its consumption, or the consumption of dependent resources, on aninterval basis, then BR will use this information in forming PSEs andclassifying timings. One example of this is: cpu, i/o, memory usageinformation that is available from zOS WLM for an aggregation ofprocesses/address spaces over a given interval.

There is also a set of information about the resource that isemployed—this information is provided as defaults in the BRMD entry forthe resource, but provided to the BR team in the form of best practicesinformation/defaults by the domain owners:

-   -   The operational state of the resource at which the observed        recovery time interval started.    -   The operational state of the resource at which the observed        recovery time interval ended.    -   The operational states of the resource at which point it can        unblock dependent resources (example: operational states at        which a DB2 could unblock new work from CICS, at which it could        allow processing of logs for transactions ongoing at time of        failure . . . ).    -   Values of statistical thresholds to indicate sufficient        observations for goal managing the resource (number of        observations, max standard deviations, confidence level).

In addition to the resources defined herein as part of the ITconfiguration that is managed, there are other resources, referred toherein as assessed resources. Assessed resources are present primarilyto provide observation data for PSE formation, and to understandimpact(s) on managed resources. They do not have a decomposed RTOassociated with them nor are they acted on for availability by BR.Assessed resources have the following characteristics, as examples:

-   -   Are present to collect observation data for PSE formation.    -   Are present to understand impacts on managed resources.    -   No decomposed RTO is associated with an assessed resource.    -   They are resources on which resources managed by BR depend upon,        but are not directly acted on for availability by BR.    -   They are resources removed (or not explicitly added) from the        actively monitored set of resources by the BR admin during RS        definition.    -   They are resources that BR does not try to recover and BR thus        will not invoke any preparatory or recovery operations on them.

Similarly, there are likely scenarios where a resource exists in acustomer environment that already has an alternative availabilitymanagement solution, and does not require BR for its availability.However, since other resources that are managed by BR may be dependenton them, they are observed and assessed in order to collect observationdata and understand their impacts on managed resources. Additionally,there may be resources that do not have alternative managementsolutions, but the customer simply does not want them managed by BR, butother managed resources are dependent upon them. They too are classifiedas assessed resources.

These assessed resources share many of the same characteristics ofmanaged resources, such as, for example:

-   -   They have an entry in the BRMD, depending on their use, and the        BRMD entry has an indication of assessed vs. managed.    -   The RS subscribes to state change notifications for assessed        resources (and possibly other notifiable properties).    -   Relationships between observed and managed resources are        possible (and likely).    -   BR monitors for lifecycle events on assessed resources in the        same manner as for managed resources.    -   Assessed resources can be added and/or removed from Recovery        Segments.    -   They can be used to contribute to the aggregated state of an RS.

Finally, there are a few restrictions that BR imposes upon assessedresources, in this embodiment:

-   -   Again, BR does not invoke any workflow operations on assessed        resources.    -   A resource that is shared between two Recovery Segments is not        categorized as an assessed resource in one RS and a managed        resource in the other. It is one or the other in the RS's, but        not both.

To facilitate the building of the customer's IT configuration,observations regarding the customer's environment are gathered andstored in an observation log. In particular, the observation log is usedto store observations gathered during runtime in customer environments,where each observation is a collection of various data points. They arecreated for each of the Recovery Segments that are in “observation”mode. These observations are used for numerous runtime andadministrative purposes in the BR environment. As examples theobservations are used:

-   -   To perform statistical analysis from the BR UI to form        characterizations of customers' normal execution environments,        represented in BR as Pattern System Environments (PSE).    -   To classify operations on resources into these PSEs for purposes        of determining operation execution duration.    -   Help determine approximate path length of operations that are        pushed down from BR to the resources, and possibly to the        underlying instrumentation of each resource.    -   Help determine approximate path length of activities executed        within BPEL workflows.    -   Finally, the data collected via the observation is also used to        update the metadata associated with the resource (i.e., in the        BRMD table) where appropriate.

BR gathers observations during runtime when “observation mode” isenabled at the Recovery Segment level. There are two means for enablingobservation mode, as examples:

-   -   1. The BR UI allows the administrator to enable observation mode        at a Recovery Segment, which will change its “ObservationMode”        resource property to “True”, and to set the polling interval        (default=15 minutes). The Recovery Segment is defined in order        to allow observation mode, but a policy does not have to be        defined or activated for it.    -   2. Once a policy is defined though and subsequently activated,        observation mode is set for the Recovery Segment (due to the        data being used in managing and monitoring the customer's        environment). Thus, it is set automatically at policy        activation, if not already set explicitly by the administrator        (see 1 above) using the default polling interval (15 minutes).

The administrator may also disable observation mode for a RecoverySegment, which stops it from polling for data and creating subsequentobservation records for insertion in the log. However, the accumulatedobservation log is not deleted. In one example, an RS remains inobservation mode throughout its lifecycle. The UI displays theimplications of disabling observation mode.

In BR, the observations that are collected by BR during runtime can begrouped into two categories, as examples:

-   -   1. Periodic poll.    -   2. Workflow (includes workflow begin/end, and workflow activity        begin/end).

A periodic poll observation is a point-in-time snapshot of theconstituent resources in a Recovery Segment. Observation data points arecollected for those resources in the Recovery Segment(s) which haveassociated BR management data for any of the following reasons, asexamples:

-   -   1. Resource has RTO properties.    -   2. Resource has operations.    -   3. Resource participates in the aggregated state for the        Recovery Segment, in which it is contained.    -   4. Resource participates in any of the six types of pairing        rules.

The full value of these observations is derived for an RS when theyinclude data that has been gathered for its constituent resources, plusthe resources that those are dependent upon. In one embodiment, theadministrator is not forced to include all dependent resources whendefining a Recovery Segment, and even if that were the case, there isnothing that prevents them from deleting various dependent resources.When defining a Recovery Segment, the BR UI provides an option thatallows the customer to display the dependency graph for those resourcesalready in the Recovery Segment. This displays the topology from theseed node(s) in the Recovery Segment down to and including the dependentleaf nodes. The purpose of this capability is to give the customer theopportunity to display the dependent nodes and recommend that they beincluded in the Recovery Segment.

Preparatory and recovery workflows are built by the BR manager toachieve the customer requested RTO policy based on resource operationstimings. During active policy monitoring by the BR manager, measurementsof achieved time for operations are recorded in observations to the logand used to maintain the running statistical data on operation executiontimes. Observations written to the log may vary in the containedresource RTO metrics and operation execution timings.

Observations are also collected from any of the BPEL workflows createdby BR in the customer's environment. There is a standard template thateach BR BPEL workflow uses. As part of that template, observation datais captured at the start of, during, and at the completion of eachworkflow. Specifically, in one example, one observation is created atthe end of the workflow with data accumulated from completion of eachactivity. This information is used to gather timings for workflowexecution for use in creating subsequent workflows at time of failure.

In accordance with an aspect of the present invention, management of acustomer's IT environment is facilitated by correlating events thatoccur within the environment, obtaining information relating to thoseevents, and performing actions, such as environment tuning or recoveryactions, based on the information. Discrete phases of processing areused to obtain the information and/or perform the actions. One or moreof these discrete processing phases have tunable time intervalsassociated therewith. For example, at least one time interval isdynamically adjusted based on the runtime state of the environment.

One data structure that is used during correlation processing is aContainment Region. A Containment Region (CR) is used at runtime toreflect the scope and impact of an event, such as an outage. AContainment Region includes a set of impacted resources and BR specificinformation about the failure/degraded state of a resource, as well as aproposed recovery. A CR is a BR internal structure. The originalresources reporting degraded availability, as well as the resourcesrelated to those reporting degraded availability, are identified as partof the Containment Region.

In one example, the Containment Region is implemented as one or more DB2tables in the Business Resilience datastore that physically resides inthe BR environment. That database is created at installation time, and aContainment Region is created and initialized (if necessary) at thattime. The CR is associated with a particular BRM, but is not used topersist any BRM resource properties. The typical access mechanism is,for instance, via JDBC calls from the BR UI client(s) and the BR managerusing JDBC type 4 drivers.

One example of a physical model of a Containment Region is depicted inFIG. 9. In one example, a Containment Region 900 includes a ContainmentRegion table 901, a Reason_For_Inclusion table 902, a Pairings_Usedtable 904, a States table 906, and a Brad_List table 908, each of whichis described below.

Containment_Region table 901 includes the singleton values associatedwith the CR. One example of the fields of this table is described below.

Data Field Data Type Description Keys CR_ID Integer Generated integerkey for Primary uniqueness via a DB2 sequence. Note all primary keys inthe BR database will be a generated integer for compatibility with othernon-DB2 databases. DISPLAY_NAME Varchar(96) Name if entered from the BRUI. User Display_Name uniqueness for CRs will be enforced by the UI.Progress Integer The index into the array of progress indicators for theCR. For example. 1. T1→T2 2. T2→T3 3. T3→T4 4. T4→T5 5. Free 6. Inuse 7.Etc. FirstEventTod Timestamp Timestamp of the first event that causedthe creation of this CR (for use in the sliding window technique).MostCurrentEventTOD Timestamp Timestamp of the most current event thatcaused an addition to this CR. CRQUState Integer The index into thearray of states for the asynchronous query build function. Forexample: 1. Initial 2. Finished 3. InProcess 4. Etc. CRQBTOD TimestampTimestamp used to place a request for resource data from the BRAD(s).T2Interval Time Time interval from the first event to T2 (used in the CRsliding window technique). T3Interval Time Time interval from the firstevent to T3 (used in the CR sliding window technique). T2TimerActiveChar(1) Flag used in the CR sliding window technique to indicate thatthe T2 timer is active. T3TimerActive Char(1) Flag used in the CRsliding window technique to indicate that the T3 timer is active.ToBeEnded Char(1) Flag to indicate this CR is to be eliminated (since amerge has happened and another CR was chosen instead of this CR).PREVENTIVE_WF_ID Integer Key into the workflow table. RECOVERY_WF_IDInteger Key into the workflow table. TS_UPDATE Timestamp Timestamp ofinitial create or last update and defaults to current timestamp.

Related to the Containment_Region table is Reason_For_Inclusion table902 that includes the reasons that a specific resource is underevaluation as potentially impacted, implicated or perpetrating by theoutage event represented by CR. In one example, Reason_For_Inclusiontable 902 includes the following fields:

Data Field Data Type Description Keys REASON_ID Integer Generatedinteger key for Primary uniqueness via a DB2 sequence. Note all primarykeys in the BR database will be a generated integer for compatibilitywith other non-DB2 databases. STATES_ID Integer Foreign key from theStates Foreign table that can be used to retrieve the list of reasonsthat a resource is in the Impacted_Resource table. Reason Integer Theindex into the array of possible reasons. For example: 1. Primary 2.Implicated 3. Question perpetration 4. Etc. TS_UPDATE TimestampTimestamp of initial create or last update and defaults to currenttimestamp.

Pairings_Used table 904 includes the pairings that caused a resource tobe in the impacted resource list. In one example, it includes thefollowing:

Data Field Data Type Description Keys PAIRINGS_USED_ID Integer Generatedinteger key for uniqueness Primary via a DB2 sequence. Note all primarykeys in the BR database will be a generated integer for compatibilitywith other non-DB2 databases. CR_ID Integer Foreign key from theContainment Foreign Region table that can be used to retrieve the listof pairings used in the formulation of the CR. RESOURCE1_ID Char(32) IDof the first resource in the pairing. RESOURCE2_ID Char(32) ID of thesecond resource in the pairing. TS_UPDATE Timestamp Timestamp of initialcreate or last update and defaults to current timestamp.

Additionally, States table 906 includes the states of each resourceassociated with the CR. In one example, this table includes:

Data Field Data Type Description Keys STATES_ID Integer Generatedinteger key for uniqueness Primary via a DB2 sequence. Note all primarykeys in the BR database will be a generated integer for compatibilitywith other non-DB2 databases. CR_ID Integer Foreign key from theContainment Foreign Region table that can be used to retrieve the listof states for the CR. RESOURCE_ID Char(32) Resource ID. STATE IntegerThe index into the array of possible states. For example: 1. Available2. Unavailable 3. Degraded 4. Etc. TS_UPDATE Timestamp Timestamp ofinitial create or last update and defaults to current timestamp.

Further, Brad_List table 908 includes the BRADs being targeted for arequest for resource data. In one example, this table includes:

Data Field Data Type Description Keys BRAD_LIST_ID Integer Generatedinteger key for uniqueness Primary via a DB2 sequence. Note all primarykeys in the BR database will be a generated integer for compatibilitywith other non-DB2 databases. CR_ID Integer Foreign key from theContainment Foreign Region table that can be used to retrieve the listof BRAD(s) being targeted for a request for resource data BRAD_IDInteger The key into the BRAD table that identifies the BRAD properTS_UPDATE Timestamp Timestamp of initial create or last update anddefaults to current timestamp

The BR manager maintains data associated with CR processing. As part ofthe BR_Manager table, data is maintained for the following, as examples:

-   -   Total number of times a CR has been built.    -   Running average of CR build time.    -   Standard deviation for CR build time.

The use of the CR during processing is described in further detailbelow. However, prior to describing the specifics associated with the CRand correlation processing, the problems to be addressed by theprocessing and various objectives to be achieved are described.

Timing Framework for Processing Events—Objectives

Outages of resources in enterprise IT customer environments are rarelyseen in isolation, as it is typical for a large number and wide varietyof resources, including servers, storage, networks, operating systemsand middleware, to operate in conjunction to meet the needs of businessapplications. However, current availability offerings do not recognizethe relationships among resources; they react to individual outageevents out of context of related failures; they have no heuristic meansfor determining how long it may take for related outages to be reported;and they have no means for bounding processing, as there is nounderstanding of recovery time objectives for the business applicationas a whole.

Customers and some vendors attempt to provide a layer of software on topof basic product deliverables to achieve a broader scope of availabilitymanagement than provided by individual products. However, these alsofall short of customer requirements, as there is no extensible frameworkfor including new resources, no formal expression of impact one resourcecan have on another, and no means to recognize related outage events. Asa result, customers face a wide variety of difficulties including, forinstance:

-   -   High cost to perform outage analysis and root cause        determination;    -   Coarse grain recovery for a broader scope of resources than        often are impacted;    -   A broader set of resources can be impacted by recovery than        necessary or effected by a failure;    -   Individualized, tailored solutions consuming large quantities of        scarce skill resources;    -   Inflexible structures which cannot adapt to changes in the        runtime IT configuration or changes in application        characteristics over the business calendar;    -   Lack of accountable recovery against service level agreements;        and    -   Hand-crafted solutions based on messages which may change,        events which are inconsistent, and automation which invokes        commands that must be coordinated across different products        having no common semantic expression for an individual resource        or operation on a resource.

Timing Framework

The above deficiencies are overcome by the processing of eventsperformed by BR. As one example, the processing is described withreference to the occurrence of errors. However, other types of eventsmay be similarly handled.

BR processing of errors is based on incoming state change notificationfor one or more resources. Each operational state change is evaluatedfor whether a new Containment Region (CR), or situation is to becreated, or whether the error is for a resource that already has anassociation or pairing with some other impacted resource. BR maintains abalance between the one extreme of reacting too quickly to a failurenotification and creating a separate CR for every failing resource, andthe other extreme of waiting so long as to jeopardize the RTO of thevarious Recovery Segments involved and/or impacted by the failure. BRaccomplishes this with the concept of an event correlation or timingframework. The predicates behind the design of the event correlationframework design are that there will very likely be multiple andassociated errors received as part of a failure and, that if BR candelay long enough to correlate events of the failure, it will havecollected the largest possible set of impacted and related resources,and yet subsequently, build the fewest, but most efficient recoveryprocesses, possible for that failure.

Within the event correlation framework, BR aggregates/correlates relatedevent (e.g., error) conditions. The window of wait time is dynamic, andbuilt on the general time for communication with the resource duringnormal communication. Once the errors are accumulated into a given CR,additionally impacted resources are identified. The entire set isassessed for state, asynchronously, to ensure that BR makes decisionswith the most current state available from a resource. Once the state isassessed, failed and degraded impacts are inspected to form a recoveryprocess.

The timing framework includes discrete steps or phases (e.g., five) eachof which may vary in duration. Techniques for adjusting the duration oftime for each phase utilize real-time data regarding the ITconfiguration, event notification of changes in the configuration,heuristic assessment of timing for event delivery, and data onprocessing time for creation and execution of a recovery set ofoperations, as examples.

Exemplary features of the timing framework include:

-   -   Formalization of a timeline for error detection, association and        processing with multiple discrete points (e.g., five);    -   Setting an interval to delay for accumulation of failures        related to initial failure;    -   Setting an interval over which accumulation of resource state        for event correlation can occur and still meet recovery time        objectives (RTO);    -   Real-time adjustment of intervals for failure event delivery and        resource state retrieval;    -   Dynamic adjustment of intervals based on, for instance, average        time to gather resource state, average time to build recovery        workflow, and average times for recovery times—used to insure        RTO continues to be met;    -   Customer adjustment of intervals.

The first event of a failure resulting from the state change on theRecovery Segment ensures the creation of a new CR. For each subsequentevent, while the Recovery Segment is in a state that is not “Available”,the event flows (e.g., immediately) to the BRM, which decides whether tocreate a new CR for the resource associated with that event, or whetherto merge the resource into an existing CR.

BR does not initiate recovery processing upon receiving the first event,but tries to delay in an attempt to determine if there are relatedfailures. The delay is bounded by the use of a “sliding window”, sinceBR can determine how long processing can wait based on a goal, such asthe RTO. Intervals are established from information that is dynamic inthe customer environment, and can further vary depending on past historyof build times for CRs. Processing for event correlation is controlledby the customer specified RTO and by, for example, two intervals whichdetermine when gathering of current resource state should begin and whenaggregation of errors is to end. The sliding window is, for instance, atimeline, that continuously adjusts as each new failure event or eachnew resource is added to the Containment Region. The sliding windowtimeline includes discrete points in time and intervals.

One example of a sliding window timeline 1000 is described withreference to FIG. 10A. As shown, the timeline includes a plurality ofdiscrete points including, for example: T1: 1st event trigger 1002; T2:CR evaluation, build 1004; T3: recovery process build initialization,window close 1006; T4: recovery process start execution 1008; and T5:recovery process end execution 1010. There are also a plurality ofintervals, including, for instance, interval T1→T2 1012; interval T2→T31014; interval T3→T4 1016; interval T4→T5 1018; and interval T1→T5 1020.Further details regarding the timeline are described below.

Sliding Window Timeline

From the time a first event (e.g., error) is reported to when BR beginsgathering current state from impacted resources is termed interval T1→T2with the point in time when BR begins gathering current state termed T2.The point in time from first reported event to when BR stopsaccumulating potentially related information (e.g., errors) for analysisis termed T3. BR provides two techniques for determining T2 and T3. Thedefault technique sets T2 at the average time required to gather queryresponses from all resources in the RS plus two standard deviations. Bydefault, T3 is set to the maximum time any resource in the RS takes torespond to a query for state. An optional dynamic technique sets T2 andT3 based on the average time to gather state from all resources in theRS, the average time to build a recovery process for the RS and theprojected time for execution of recovery operations included in the CR.A third option enables customers to specify T2 and T3 as either fixedtime intervals or time intervals calculated from simple arithmeticoperations on the average and standard deviation of resource response toquery time.

Further details regarding discrete phases T1-T5 are described below.

-   -   T1 is the point in time of the first event (e.g., failure event)        in the current sequence that triggered the creation of a        Containment Region.    -   T2 interval, which is adjustable, is the time from the first        reported event (e.g., error) to the time that BR is to start        collecting current state from the impacted resources for        analysis of the set of related failures. BR explicitly gathers        state from the impacted set of resources to ensure their value        for state is more recent than the last event received. By        default, T2 interval is initialized from the average time        required to gather state query responses from all resources in        the RS plus two standard deviations. The statistics on average,        standard deviation and maximum time for resource state query are        maintained by BR based on ongoing, periodic polling for resource        information. BR measures time intervals for making queries of        resource state. By using measurements of resource state query,        BR adjusts to the customer configuration and the level of        utilization of IT resources. By being based on the average        response to resource query, the default T2 interval and T3        interval are dynamically calculated based on a history of event        delivery delays experienced in the customer's normal,        pre-failure environment. Using resource state query response        times that reflect the customer environment at time of error        assists BR in determining the set of related events for analysis        (e.g., failure analysis).    -   Once the T2 interval is expired and the T2 point in time        reached, and BR detects that most failed resources are likely to        have reported a failure, BR explicitly gathers state from the        impacted set of resources to ensure their value for state is        more recent than the last event received. The state information        is to be verified explicitly since the eventing mechanisms may        have an unbounded delay. Further, in one embodiment, the        information is not queried synchronously, since gathering state        is performed in a time critical path, and queries that do not        show a response are terminated in a time interval aligned with        achieving the required RTO. In one implementation, these state        queries are accomplished with the BR Asynchronous Distributor        (BRAD).    -   T3 is referred to as the point in time when the sliding window        has closed. By default, T3 interval is initialized based on the        maximum time that any resource in any RS affected by the outage        takes to respond to a query for state. Customers may choose the        BR provided technique which sets T3 interval based on historical        information on gathering resource state information, time to        generate the recovery process and time for recovery operations        to execute. Customers may alternatively choose to specify T3        interval based on average time and maximum time required to        gather resource state. In one example (e.g., dynamic technique        described herein), the average time to gather state for        resources impacted by an outage is maintained by BR. This        average (referred to herein as avg23) is used to determine the        spacing of the interval between T2 and T3 in the dynamic        technique. T3 is the point in time that the creation of the        recovery process begins.    -   Once the T3 time interval expires for any CR, the sliding window        for that CR is closed to incoming errors, and the resources for        any other errors go into the formation of a new CR. If event        notification is received for resources related to a CR in the        process of gathering resource state and property data, that        event will be incorporated into the CR it is related to, and        processing to gather resource state and property data        reinitiates. As a result, multiple queries for resource state        and property value may be concurrently in process for a CR.        Processing is coordinated for initiating query requests and        receiving query responses to insure the most current resource        state and property values are utilized in evaluating the        failure.    -   T4 is the point in time that the recovery process begins        execution.    -   T5 is the point in time that the recovery process is projected        to end based on operation execution duration timings. It should        end, in one embodiment, prior to the RTO of the impacted        Recovery Segment(s).

The timing framework for event correlation is established and alteredover the T1→T5 interval. Initial values for T1→T2 and T2→T3 areestablished when a new CR is formed. Times T1→T2 and T2→T3 are adjusted,if subsequent failure events are related to a previously formed CR.Recognition of related failures may occur as a result of a new failureevent being received or as the result of gathering state informationfrom resources (e.g., using an AsynchQueryBuild routine, describedbelow). For instance, as shown in FIG. 10B, at each new event E (1030),as new resources are added to the Containment Region, the T2 point intime is adjusted (1032) to account for the state query of those newresources.

The timing framework, when initially formed, sets timers to expire at T2and T3. In particular, timers are established for the expiration of theT1→T2 interval and the T2→T3 interval. Further details regarding T2 andT3 interval expiration are described below.

T2 Expiration

An interval timer is established initially when a new CR is created.Adjustments to the interval may be made as subsequent events occur whichare related. Adjustments to the timer may also be made when responses toresource state are received that add to the set of resources impactedand included in the CR. When the T2 interval timer expires, theAsynchQueryBuild routine is invoked. Processing also updates the statusof the CR to indicate it is in the T2 to T3 phase of processing.

The T2 timer may be cancelled if during event processing or response toresource state processing it is determined that the current time islater than when the T2 timer was to expire. T2 timer intervals of CR(s)which are ended during CR processing are also cancelled.

T3 Expiration

The interval timer for expiration of the T3 interval gives control to aCloseSlidingWindow routine, described herein. The CR progress is updatedto reflect processing being in the T3→T4 phase. If responses to allqueries for resource status subsequent to the most recent eventnotification related to the CR have not been received, control is passedto processing which substitutes cached resource state and propertyvalues for missing resource status responses. Otherwise, control ispassed to processing to formulate the recovery process.

The T3 timer may be cancelled if during event processing or response toresource state processing it is determined that the current time islater than when the T3 timer was to expire. T3 timer intervals of CR(s)which are ended during CR processing are also cancelled.

Establishing Time Intervals

There are, for example, three techniques available for establishing thetime intervals in the timing framework:

-   -   1. The default routine (a.k.a., fixed routine) uses historical        timings for receiving responses to periodic polling for resource        data, which is maintained as a running set of statistics on        average response time, standard deviation of average response        time and maximum event response time for any resource in the RS.        Retrieval of resource status may be achieved in a variety of        ways including: direct message passing requesting data from a        service provided by the resource; monitoring of events published        by the resource as may be done using SNMP (Simple Network        Management Protocol) or CIM (Common Information Model);        monitoring messages produced by the resource for notification to        operational staff; notification provided through notification        services or protocols, etc. However resource state is obtained,        a characteristic of the technique that is employed is that the        timing for receiving event status be monitored, and that a        similar mechanism be used to notify the BRM of resource outage        as is used to monitor for resource state change.    -   2. A second way of establishing timing intervals for the        framework is through direct customer specification of T2 and T3        times, which are based on historical information on average        response time, standard deviation of average response time and        maximum event response time for any resource in the RS.    -   3. A dynamic technique is provided as a third option which        utilizes statistics regarding the time to form the recovery        process (average and standard deviation) and estimates recovery        process execution duration based on operations that are required        to recover the failed environment.    -   In particular, the dynamic technique establishes T2 and T3        intervals based on, for instance, the projected recovery time,        the specified RTO, average time to gather resource state and        average time to build a recovery process.

Processing in the time interval from T2 to T3 is managed by theAsynchQueryBuild technique. A query for data on resources included inthe CR is initiated and responses to query requests are processed asthey are received. If, during this asynchronous build process, the BRMdetects that there are overlapping resources in multiple CRs, whichindicates that errors have been detected that impact related resources,the two CRs are merged into a single CR. Each time resources are addedto the CR after the initial query for resource data, a new request forresource data is initiated for each resource in the CR. TheAsynchQueryBuild process determines the most current response whenmultiple query requests are initiated.

The AsynchQueryBuild processing phase of the timing network ends whenthe T3 time interval expires with a timer driven event. It may also bedetected as ended when processing responds to query requests bycomparing the current time of response processing to the established T3interval. When ended, it may be true that not all requests for resourcedata have received a response. For any missing responses for resourcedata, the previously cached resource data from the most recent periodicpoll interval is used. The output of the Asynchronous Build process isan array of resource states that are used in generating a recoveryprocess.

The T3→T4 interval is the time to build the recovery process (or takeother action). For the dynamic technique provided by BR, the averagetime to build the process for recovery is maintained by BR. This average(referred to herein as avg34) is used to determine the interval betweenT3 and T4.

A projection of recovery time covering the interval from T4→T5 is made,for the dynamic technique, based on, for instance, historicalinformation on recovery operation execution times. Operation timings canbe specified by the customer or based on historical measurements. In theembodiment herein, operation timings are associated with a customerconfiguration, termed a Pattern System Environment (PSE). Operatingtimings for recovery are used in conjunction with operation dependenciesand operation ordering requirements to build a programmatic Gantt chartreflecting recovery operation sequences. From the Gantt chart, aprojected recovery operation time is derived (referred to herein asprojected45).

The framework for event timing is designed to run based on timers set totransition between discrete steps in the process. However, as thetechnique depends on the passage of real time, there exists thepotential for processing to be stopped or delayed. Examples include:error correction processing of the computer system; stop conditionsmanually or programmatically occurring during processing; and/ordisabling for interrupt processing time of the computer system. Sincereal time can pass without the assurance of the provided for timerinterrupts, checks are included within the technique to determine if thecurrent real-time is past the time where T2 or T3 should havetransitioned the technique to a subsequent step.

Multiple mechanisms may be employed to determine if stop conditions haveoccurred. One technique tests for expired intervals explicitly.Alternatively, the timer services may be utilized which accept a time ofday (TOD) value when setting a timer. If the current TOD is past the TODfor which notification is requested, an error indication may be returnedby the timer service. Alternatively, the timer service may set the timerand have it immediately expire. In all cases, there exists a delaybetween the time when a timer is requested to be set and when thatrequest is processed. If hardware is utilized to establish the timer, apotential exists for the computer system to be stopped before thehardware is initialized. There exists a potential of not receiving thetimer event if the computer system is not enabled for notification fromthe hardware. If software timing services are utilized, there exists aduration of time where the software may not be operational to providenotification of time duration expiration.

Description of Sliding Window Technique

One embodiment of the logic to calculate intervals is described withreference to FIGS. 11A-11E. In one example, this logic is performed bythe BRM component of the BR system. Prior to describing the specifics,however, a summary of the processing is provided.

To set T2 and T3, the following processing occurs, in one example.

-   -   Determine if BR dynamic, BR fixed or a customer specified        routine is current for the RS.    -   Calculate both an initial value for T2 and T3, as well as time        remaining to T2 and T3 from when the first error was reported        for events reporting subsequent errors that have been merged        with the CR.    -   For BR dynamic technique:        -   Project a time (projected45) for the interval T4 to T5 for            recovery operation execution based on operation timings in            the one current PSE for a non-shared resource or on the            average of operation timings from all current PSEs for a            shared resource.        -   Create a Gantt chart from the list of recovery operations            accumulated.        -   Determine recovery operation time from the Gantt chart            representing operation ordering and operation overlap.        -   Determine T2 and T3 intervals and point in time TOD values            from avg23 time (average time to gather resource state),            avg34 time (average time to build recovery workflow), and            projected45 time from the recovery operation execution            duration time and RTO.    -   For BR fixed technique:        -   T2 interval and point in time TOD are set from the average            of resource state query times for the RS associated with the            CR having the smallest RTO.        -   T3 interval and point in time TOD are set to the largest            time for a resource to respond to a query for state from the            set of resources associated with the set of RSs associated            with the CR.    -   For customer technique:        -   T2 interval and point in time TOD are set from the RS having            the smallest RTO as either fixed or calculated from the avg            and std dev of resources in that RS response to query.        -   T3 interval and point in time TOD are set from the RS having            the resource with the longest response to a query for state            as either fixed or calculated from the average, standard            deviation and maximum of resource response to query times.    -   Intervals are returned for time to T2 and T3.

As described with reference to FIGS. 11A-11E, CalculateInterval Windowcalculates intervalT2 and intervalT3 for both initial event and timeleft conditions. It is invoked when a Containment Region is initiallycreated, when a new event is merged into a Containment Region or whenContainment Regions are merged as a result of response to status queryprocessing, as examples.

Referring initially to FIG. 11A, from the set of RS(s) recorded asaffected in the CR, the one with the smallest RTO is selected, STEP1100. This is the time within which processing of the event timingframework is to complete. It is saved in a variable, RTO_To_Wait, STEP1102. Thereafter, a determination is made as to whether the dynamictechnique is to be used, INQUIRY 1104. If the dynamic technique is to beused for the RS, processing continues by determining dependency orderoperations, STEP 1106.

In one example, dependency operation ordering logic builds an orderedset of operations taking into account dependencies between resources andtheir operations. The input to the logic is a set of operations onresources, some of which may require including other dependentoperations. The output is an ordered list of operations, including anydependent operations not originally in the list. In this implementation,the information on dependency of operations is determined using pairingconstructs that describe the relationships between resources. In otherimplementations, information on dependencies between operations could bedescribed in a relational table, or other external file. In a furtherimplementation, the priority of operations to consider in the chain ofdependent operations can be included in the logic. The processing fordependency operation ordering is, for instance, a three pass process. Inthe first pass, the set of input operations are analyzed and anydependent operation is incorporated into the set. In the next pass, theoperations are separated into stages such that any operations that canoccur in parallel are put into the same stage, and ones that occur laterare moved to subsequent states. In the final pass, each operation,resource pair in the ordered list is updated with a list of operationsthat are to occur after the pair. This list is represented as an arrayof indexes, where each index value is identifying a specific operation,resource pair in the ordered list.

Thereafter, a Gantt chart is built, STEP 1108. In one example, aBuild_Gantt_Chart routine is invoked to build a programmaticrepresentation of a Gantt chart, which takes as input a set of data onoperations and creates output, which includes a matrix of operations andtimings, along with an overall maximum time for operation execution.Input to the routine includes a set of data, ordered_op_list, which haselements that include a set of data on each operation, opentry. Elementsof the set are in execution order sequence, as one example. Each opentryelement includes, for instance: a resource identity, operation, sequencenumber of operation, operation execution time and a list of the index(s)into the ordered_op_list for operation(s), if any exist, which are tooccur after the operation in the element (e.g., resource, op, seq#,op_exec_time, op_after(n)). The matrix generated by the routine hasthree columns and one row for each input operation. The first column ofeach row includes the input data on a resource/operation, the secondcolumn is the start time relative to 0 for the operation, and the thirdcolumn is the end time relative to 0 of the operation. Additionally, afield is returned, maxtime, which is the maximum time for execution ofthe set of operations.

Processing is performed in two phases. In the first phase, a table isbuilt that includes one row for each unique path through the sequence ofoperations. The input ordered_op_list is indexed by the variablei_ordered_op_list. The result of phase one processing is a table,outlist_table. The index i_next_available_row indicates the row withinoutlist_table where the next unique sequence through the set ofoperations will be built. Processing proceeds by locating each inputoperation with the lowest operation sequence number. Each of these is aroot of unique paths through the set of operations. The set of theseoperations is processed sequentially with unique paths through the setof operations for the first root completing before processing the uniquepaths through the set of operations for the second root.

Processing for a root begins by assigning the current row in theoutlist_table to the index current_orow_index and incrementing thei_next_available_row index. Within the row being processed, an index tothe current operation being processed is maintained, index_for_ops.Processing proceeds through the list of operations in the input. A newrow is created in outlist_table when more than one input operation is tooccur after the current operation being processed. Two indicators arekept with each row of the outlist_table. The row_changed indicator isused to cause a copy of the row to be made before a new operation whichis to occur later in the sequence is added. Associated with each rowthere are two fields used to save progress in processing the sequence:ordered_op_next is an index into the input ordered_op_list for the lastoperation in the sequence; op_next is an index into the row for the lastoperation in the sequence. Entries in the row include the index into theinput ordered_op_list for operations comprising the sequence.

When a new row is created, it is initialized with the sequence ofoperations in the current row that have been accumulated to that pointof processing. The second indicator associated with each row, row_end,is used to identify a row which is a complete path through the sequenceof operations.

The next row is processed in the same manner as the first row of a root.Processing for a root is determined to have recorded every unique paththrough the sequence of operations when there were no copied rows madeduring processing of the current row. When all unique paths through theset of operations for the first root has completed, processing continueswith the second and subsequent roots.

The second phase of processing builds the output of the routine,Gantt_table and maxtime. The maximum time for execution of the sequenceof operations is set in maxtime. The Gantt_table includes one row foreach opentry in the ordered_op_list input. An entry in the Gantt_tableincludes the opentry provided as input, a start time relative to 0 andan end time relative to 0 for the operation.

The Build_Gantt_Chart routine returns an overall time required forexecution of the operations required for recovery processing. This timeinterval is saved in Estimated45 (a.k.a., projected45; set by maxtimereturned from Gantt routine), STEP 1110.

In order to calculate the time required for all resources in the CR torespond to a request for state, a list of resource response times iscreated. The List_Responset is initially set to null, STEP 1112. Foreach resource in the CR, STEP 1114, the average response to poll timefor the resource is included in the List_Responset, STEP 1116.Thereafter, the average and standard deviation for response to polltimes for the resources in the CR are calculated, STEP 1118 (FIG. 11B).The time interval between T2 and T3, AvgT23, is set to the average andtwice the standard deviation for response times of resources currentlyin the CR, STEP 1120.

The time elapsed from first event notification until the current time iscalculated and saved in time_used, STEP 1122. The time required to buildthe recovery process, Avg34, is based on historical data maintained inthe BRM table. The average of previous recovery process build times plustwice the standard deviation is calculated and saved in Avg34, STEP1124.

The T3 interval is set to RTO_To_Wait minus Estimated45 minus Avg34minus Time_Used, STEP 1126. T2 interval is set to the T3 interval justcalculated minus Avg23, STEP 1128.

Processing is to insure the time intervals calculated have not alreadyexpired. If the T3 interval is negative, INQUIRY 1130, it has alreadyexpired. A value equal to the Time_Used minus one is returned toindicate the T3 interval has expired, STEP 1132. If the T3 interval hasalready expired, the T2 interval has also expired. Thus, the T2 intervalis set to Time_Used minus 2 to reflect T2 interval expiration, STEP1134.

Returning to INQUIRY 1130, if the T3 interval has not expired, the T2interval is tested for expiration, INQUIRY 1136 (FIG. 11C). If the T2interval has not yet expired, the technique returns T2 and T3 intervalsfrom the current time. If the T2 interval has expired, the T2 intervalis set to Time_Used minus 1 to reflect T2 interval expiration, STEP1138.

Returning to INQUIRY 1104 (FIG. 11A), if the dynamic technique is notcurrent for the RS, a determination is made as to whether the fixed(a.k.a., default) technique is current for the RS, INQUIRY 1140 (FIG.11D). If the default technique is current for the RS, processingcontinues to set the T2 and T3 interval based on response to periodicpolling statistics. T2 is set to the average polling event responsesplus twice the standard deviation less time already elapsed ascalculated from the current TOD minus the first event TOD in the CR,STEP 1142. The T3 interval is set to the maximum poll event plus twostandard deviations minus the time already elapsed as calculated fromthe current TOD minus the first event TOD in the CR, STEP 1144.Processing then continues to check for T3 and T2 expiration at INQUIRY1130 (FIG. 11B).

Returning to INQUIRY 1140 (FIG. 11D), if the fixed technique is notcurrent for the RS, then customer provided timings are to be applied.Thus, a determination is made regarding calculated or fixed timings,INQUIRY 1148 (FIG. 11E). For fixed T2 timings, T2 is set to the fixedvalue provided minus the elapsed time as calculated from the current TODminus the first event TOD in the CR, STEP 1150. Thereafter, processingcontinues at INQUIRY 1156, described below

Referring again to INQUIRY 1148, for arithmetic calculation of T2, theprovided formula is applied to event response time statistics in the RS,STEP 1152. The T2 interval is set to the calculated time interval minustime already elapsed as calculated from the current TOD minus the firstevent TOD from the CR, STEP 1154. Processing then continues to INQUIRY1156.

At INQUIRY 1156, if a fixed T3 customer provided time is to be utilized,the T3 interval is set to the specified time interval minus time alreadyelapsed as calculated from the current TOD minus first event TOD fromthe CR, STEP 1158. Otherwise, the provided formula is applied to theevent statistics from the RS, STEP 1160, and the calculated time islessened by the amount of already elapsed time and returned as the T3interval, STEP 1162.

Processing continues with checking for T2 and T3 having already expired,INQUIRY 1130 (FIG. 11B). This concludes description of the CalculateInterval Window Logic.

The Calculate Interval Window logic is used, for example, in creating anew CR for the timing framework, as described below.

New CR Processing for Timing Framework

One embodiment of the logic associated with new CR processing for thetiming framework is described with reference to FIG. 12. In one example,this logic is processed by the BRM component of the BR system.

On first event notification, the timing framework is set up as part ofcreating a new CR. The FirstEventTOD field is set in the CR equal to thecurrent TOD, STEP 1200. Further, the CR progress indicator is set to theT1→T2 phase, STEP 1202, and the CalculateIntervalWindow routine isinvoked, which calculates and returnes T2interval and T3interval, STEP1204, as described above.

If the T3 interval has expired, INQUIRY 1206, which is determined, inone example, by comparing FirstEventTOD from the CR added to theT3interval with the current TOD, a CloseSlidingWindow routine (describedbelow), is invoked, STEP 1208. This check detects delays in processingwhich have progressed real time beyond the end of the time when resourcestatus requests are to be processed. The CloseSlidingWindow routineprogresses the CR to the next phase of processing.

If the T3 interval has not expired, INQUIRY 1206, an interval timer isset for the T3 interval with timer expiration to give control to theCloseSlidingWindow routine, STEP 1210.

Moreover, if the T2 interval has expired, INQUIRY 1212, which isdetermined, in one example, by comparing FirstEventTOD from the CR addedto the T2interval with the current TOD, the Asynch Query Build routineis invoked, STEP 1214. This check detects delays in processing whichhave progressed real time beyond the end of the time when requests forresource status are to be initiated.

Returning to INQUIRY 1212, if the T2 interval has not expired, aninterval timer is set for the T2 interval with timer expiration to givecontrol to the Asynch Query Build routine, STEP 1216. This concludesdescription of the New CR processing logic.

Customer Modification of Timings

As described above, customers may specify T2 and T3 as either fixed timeintervals or time intervals calculated from simple arithmetic operationson the average and standard deviation of resource response to querytime.

One embodiment of the logic employed by customers to modify timings isdescribed with reference to FIGS. 13A-13C. In one example, thisprocessing is invoked by UI and performed by the RS component of the BRsystem.

Referring initially to FIG. 13A, selection of the RS for which timingsare to be provided may be performed by starting with the list of definedBRM(s) presented through the UI, STEP 1300, from which a specific BRMmay be selected, STEP 1302. For the selected BRM, the set of relatedRS(s) is presented, STEP 1304, from which a specific RS may be selected,STEP 1306. Alternatively, the RS to be modified can be specifieddirectly (hence, Start 2).

Thereafter, a determination is made as to whether the RS state is beingactively monitored for availability, INQUIRY 1308. If the RS is notactively being monitored for availability, an error is presented via theUI, STEP 1310, and processing ends. Otherwise, for an actively monitoredRS, the average and standard deviation of event responses to periodicpolls and the maximum time for a response to periodic polls, along withthe standard deviation, are presented, STEP 1312.

Further, since intervals may be specified as fixed values or as simplearithmetic formulas, a request is made, via the UI, for a formula orfixed T2, STEP 1314. If a formula for T2 is specified, INQUIRY 1316, theformula is applied to the current event statistics for validation, STEP1318. Thereafter, or if a formula for T2 is not specified, a request fora fixed T3 or formula specification is made via the UI, STEP 1320 (FIG.13B). If a formula for T3 is specified, INQUIRY 1322, the formula isapplied to the current event statistics for validation, STEP 1324.Thereafter, or if a formula for T3 is not specified, processingcontinues with validation of the values for T2 and T3.

Validation of the values provided for T2 and T3 has multiple steps. In afirst step, T3 is verified to be greater than T2, INQUIRY 1326. If T3 isnot greater than T2, an error is presented along with the T2 and T3values, STEP 1328, and processing returns to interval specification,STEP 1312 (FIG. 13A). Otherwise, of the resources associated with theRS, the minimum and maximum event response times are determined, STEP1330 (FIG. 13B). If the interval from T2 to T3 is less than either theminimum or maximum event response times, INQUIRY 1332, a warning messageis generated as some responses or all responses may not be expected toarrive in the specified window, STEP 1334.

Thereafter, or if the interval is not less than the minimum or maximumevent response times, validation continues by selecting the PSE forwhich validation of the RS goal has a minimum RTO, STEP 1336. Theresource recovery operation having the largest and smallest operationexecution duration times are determined, STEP 1340 (FIG. 13C). If theminimum RTO less the T3 interval is less than the projected recoverytime for the total RS, INQUIRY 1342, insufficient time is provided forrecovery of the entire RS given the T3 specification. Thus, a warning isissued via the UI, STEP 1344. Thereafter, or if RTO less the T3 intervalis not less than the projected recovery time for the total RS,processing continues with INQUIRY 1346. If the RTO less the T3 intervalis less than the longest recovery operation execution duration, INQUIRY1346, insufficient time is provided for recovery of some of theresources associated with the RS given the T3 specification; thus, awarning is issued via the UI, STEP 1348. Thereafter, or if it is notless, if the RTO less the T3 interval is less than the shortest recoveryoperation execution duration, INQUIRY 1350, insufficient time isprovided for recovery of any resource associated with the RS given theT3 specification; thus, an error is issued via the UI, STEP 1352, andprocessing continues at interval specification, STEP 1312 (FIG. 13A).

When valid specification of T2 and T3 interval has been achieved, the RSis updated with the interval and an indication of customer providedinterval specification, STEP 1354 (FIG. 13C). This completes processingof the customer modifications to timings.

Asynch Query Build and Close Sliding Window

In various processing described above, (e.g., T2, T3 Expiration and NewCR Processing for Timing Network), an Asynch Query Build routine and aClose Sliding Window routine are employed. Further details relating tothese routines are described below.

Asynchronous Query Build

When an intermediary interval is reached in the timeline for a CR and BRhas detected that most failed resources are likely to have reported afailure (T2 point in time and at expiration of T2 interval), BRexplicitly gathers state from the impacted set of resources to ensuretheir value for state is more recent than the last event received. Thisis accomplished via the Asynchronous Query Build routine, which isinvoked via expiration of a timer interval and is performed by the BRMcomponent of the BR system. As the name implies, this routine runsasynchronously, in this embodiment.

In the phase where BR is still accepting related incoming errors, the CRis built to include only related resources that are one step away in agraph. In ballooning the CR further, the pairing information in the BRRD(e.g., impact assessment rules) is used to determine whether there is animpact to other resources and to build out the CR to include the fullset of impacted resources.

As part of this asynchronous query build process, if it is detected thatresources in the CR impact other resources, such that they become failedand/or degraded (based, for instance, on operation impact pairingrules), these impacted resources are added to the CR to help creation ofthe recovery process.

From pairings, it is determined if there are other resources which couldcause a resource in the CR to become failed or degraded. Theseperpetrating candidates are added to the CR with a reason as questioningtheir perpetration, qperp. Thus, resource data is retrieved. Analysis ofthe root cause determines if a resource is failed or degraded and ifreported explicitly, implicated from a pairing, or retrieved based onbeing questioned as a perpetrator.

During this process, the CR is ballooned, which means that if it isdetected that resources in the CR impact other resources such that theybecome failed and/or degraded (based on operation impact pairing rules),these impacted resources are added to the CR as well; multiple CR's maybe merged, if there are intersections found that are not just at the RSlevel; resources which may have caused other CR included resources tobecome failed or degraded based on impact pairings are included in theCR for query processing; and asynchronous requests to the appropriateBRAD(s) are sent.

Referring to FIG. 14A, input to AsynchQueryBuild is the CR for whichprocessing is to be performed. The CR is retrieved and serialized, STEP1400. Since multiple concurrent processes may have attempted to invokethe AsynchQueryBuild routine, a check is made to determine if processingis required, e.g., if CRQBState is initial and the CRQBTOD matches theMostCurrentEventTOD, INQUIRY 1401. If processing is not to be performedby this instance of AsynchQueryBuild, processing is terminated.Otherwise, the CR is updated to reflect CRQBState is in process, STEP1402, and the CR is externally recorded in the CR table, STEP 1403. Ifthe update fails, INQUIRY 1404, the processing of AsynchQueryBuild isrestarted.

Otherwise, an in-memory list of resources from the CR is created,ImpactedResList, from the resource information in the CR (e.g.CR.States), STEP 1405. Data initialized in the ImpactedResList includesthe resource, resource(s) which caused it to be in the CR, resourcestate and reason(s)—e.g., failed, degraded, implicated, questionperpetration. Further, an index for processing the ImpactedResList isinitialized to the top of the list, STEP 1406.

If there are resources to be processed, INQUIRY 1407 (FIG. 14B), foreach resource in the ImpactedResList, the BRMD is retrieved withoutserialization, STEP 1408. The resource state from the BRMD is used toupdate the ImpactedResList as additional periodic poll or query eventsmay have caused the BRMD to be updated, STEP 1409. If the resource hasaggregated state, INQUIRY 1410, an evaluation of aggregated state isperformed using cached data for other resource state andproperty/values, STEP 1411. The calculated aggregated state is saved inthe ImpactedResList, STEP 1412.

Thereafter, or if the resource does not have aggregated state, impactpairings with a matching Resource 1 index are retrieved from the BRRD,STEP 1413. This reflects the resources which may become failed ordegraded as a result of this resource being failed or degraded. Triggerconditions for the pairings are evaluated, STEP 1414, to determine ifthe pairing is applicable at this point in time. Each pairing isprocessed until all pairings for this resource have been evaluated, STEP1415 (FIG. 14C), and then, the next resource in the ImpactedResList isto be processed, STEP 1416.

For the pairing, Resource 2 is tested as to whether it is from a pairingin the ImpactedResList, INQUIRY 1417. If an array entry exists forResource 2, data on the resource are updated, including, for instance,ReasonForInclusion, State and Reason, STEP 1418. The pairing is added tothe pairings used in forming the CR, CR.PairingsUsed, STEP 1419, andprocessing continues at STEP 1415.

Returning to INQUIRY 1417, if Resource 2 from the pairing is not alreadyin the ImpactedResList, it is added in a new array entry, STEP 1420.Resource 2 is also added to the CR.States array in a new entry, STEP1421. Data for Resource 2 are updated in the ImpactedResList, STEP 1422,and in the CR.States array, STEP 1423, including, for instance,ReasonForInclusion, State and Reason. The mechanism for requestinginformation about the resource is also saved as part of the Resource 2data, e.g. the BRAD, in one implementation, STEP 1424.

If Resource 2 has aggregated state, INQUIRY 1425, the aggregated stateis evaluated using cached data for other resources, STEP 1426, and savedin the ImpactedResList, STEP 1427, and the CR.States array, STEP 1428.The pairing is added to the CR, STEP 1419, and the next pairing isevaluated, STEP 1415.

If Resource 2 does not have aggregated state, INQUIRY 1425, processingcontinues with STEP 1419. When all pairings have been evaluated for thecurrent resource, the next resource in the ImpactedResList is selectedfor processing, STEP 1416.

Returning to INQUIRY 1407, when all resources identified with the CR tothis point have been processed, an evaluation of CR merge requirementsis made. First, the CR(s) associated with this BRM which are in a phaseof accepting new events, T1→T2, or querying resource data, T2→T3, areselected from the CR table, STEP 1429 (FIG. 14D). The list of CR(s)returned is processed one at a time, INQUIRY 1430, with the next listentry being selected, STEP 1431. An intersection of resources in theCR.States array and the ImpactedResList array is formed, STEP 1432. Ifthe intersect is null, INQUIRY 1433, the next CR entry is processed,INQUIRY 1430. Otherwise, the CR with intersecting resources is added tothe CR_List, STEP 1434, and processing returns to INQUIRY 1430.

When all CR(s) returned have been processed, INQUIRY 1430, those that donot have intersecting resources are unlocked, STEP 1435. If the CR_Listhas a single entry, INQUIRY 1436, processing to merge CR(s) is notneeded, and thus, processing continues at STEP 1455 (FIG. 14G), asdescribed below. Otherwise, the CR from the CR_List having the oldestfirst event TOD is selected, STEP 1437 (FIG. 14D) and all other CR(s) inthe CR_List are deselected.

For each deselected CR from the CR_List, STEP 1438 (FIG. 14E), anindicator is set for CR processing to end, ToBeEnded, STEP 1439. Eachresource in the deselected CR is processed, STEP 1440. If the resourceexists in the ImpactedResList already, INQUIRY 1441, a comparison ofdata on the resource in the CR.States array entry and theImpactedResList is made to determine if an update of the ImpactedResListentry is required, INQUIRY 1442. If so, the ReasonForInclusion, Stateand Reason from the CR.States array entry is added to the array entry inthe ImpactedResList, STEP 1443, and the selected CR.States array entry,STEP 1444. Processing then continues at STEP 1440.

Returning to INQUIRY 1442, if an update is not required, then processingflows to STEP 1440.

Returning to INQUIRY 1441, if the resource did not already exist in theImpactedResList, it is added along with data on ReasonForInclusion,State and Reason to the ImpactedResList, STEP 1445, and the selectedCR.States array, STEP 1446. Processing then continues at STEP 1440.

When all resources have been processed for the CR, STEP 1440, thepairings from the deselected CR are merged with the pairings in theselected CR, STEP 1447 (FIG. 14F). If the T2 interval timer for thedeselected CR has been set, INQUIRY 1448, it is cancelled through, forinstance, invocation of system services, STEP 1449. Thereafter, or ifthe T2 interval timer is not set, if the T3 interval timer for thedeselected CR has been set, INQUIRY 1450, it is also cancelled through,for instance, invocation of system services, STEP 1451. Thereafter, orif the T3 timer is not set, the deselected CR is prepared for reuse bysetting the CR.Progress indicator to Free, STEP 1452. Latent resourcedata query responses are discarded as a result of updating the mostrecent event TOD, CR.MostRecentEventTOD, STEP 1453. Also, the deselectedCR is recorded in the CR table and serialization is released, STEP 1454,and processing continues at STEP 1438 (FIG. 14E).

When the deselected CRs are processed, processing continues with INQUIRY1455 (FIG. 14G). Similarly, if no CR merge processing is required,INQUIRY 1436 (FIG. 14D), processing continues at STEP 1455.

When CR merge processing has completed, INQUIRY 1438, or is notrequired, INQUIRY 1436, AsynchQueryBuild searches for resources whichhave not reported an event, but which may have been the cause of“failed” or “degraded” reported events. Processing begins by forming adirected acyclic graph (DAG) of the resources in the CR.States arrayusing the saved pairings used, STEP 1455 (FIG. 14G). An index to addresources to the end of the list of impacted resources (ImpactedResList)is set to the current end of the array, STEP 1456. For each leaf node inthe DAG, there exists the possibility of a perpetrating resource whichcaused the reported event.

Thus, for each leaf node in the DAG, STEP 1457, impact pairings with theleaf node as Resource 2, the effected resource, are selected from theBRRD table, STEP 1458. Trigger conditions for the returned pairings areevaluated using unserialized BRMD data to determine if the pairing iscurrently applicable, STEP 1459.

For each returned pairing which is currently applicable, STEP 1460, thepairing is added to the parings used in building the CR, CR.ParingsUsed,STEP 1461. If Resource 1 from the pairing is already in theImpactedResList, INQUIRY 1462, the next pairing is evaluated, STEP 1460.Otherwise, Resource 1 is added to the ImpactedResList in the arraylocated by the index for adding perpetrating resources, STEP 1463. TheReason for the resource being part of the CR is indicated as questioningperpetration, qperp. Resource 1 is also added to the CR.States arraywith Reason qperp, STEP 1464. The mechanism to request data regardingResource 1 is saved, STEP 1465, and the next array location for addingperpetrating resources to ImpactedResList is updated, STEP 1466, beforeevaluating the next pairing, STEP 1460.

Processing continues for the pairings for each leaf node. Thereafter,having located the first candidate for perpetrating resources being inthe CR, the chain of resources having the ability to result in theperpetrating resource being failed or degraded is processed with eachnode in the chain added to the CR for evaluation as a perpetratingresource. Processing begins by setting an index for additions to theImpactedResList where the first available array entry exist, at iqperp,STEP 1467 (FIG. 14H). The index into the ImpactedResList forperpetrating resources is reset to the beginning of the perpetratingresource candidates, ires, STEP 1468. When the last perpetratingresource candidate has been evaluated, INQUIRY 1469, processingcontinues by forming request messages for resource data, STEP 1480 (FIG.14I), as described below.

However, if there are still more perpetrating resource candidates to beevaluated, INQUIRY 1469 (FIG. 14H), processing continues, as describedherein. Processing for a perpetrating resource may add entries to theImpactedResList as pairings are evaluated which identify the potentialfor impact of one resource to effect another already in the CR. Impactpairings with Resource 2 matching the perpetrating resource beingprocessed are retrieved from the BRRD, STEP 1470. Trigger conditions forthe returned pairings are evaluated to determine if the pairing iscurrently applicable, STEP 1471.

For each pairing evaluated as currently applicable, STEP 1472, thepairing is added to the list of pairings used to form the CR, STEP 1473.If Resource 1 from the pairing (i.e., the resource for which a changemay cause a failed or degraded condition) is already in theImpactedResList, INQUIRY 1474, the next pairing returned is selected forevaluation, STEP 1472. Otherwise, Resource 1 from the pairing is addedto the ImpactedResList at the end, STEP 1475, and added to the CR.Statesarray with Reason set to qperp, STEP 1476. The mechanism to requestresource data regarding resource 1 is saved, STEP 1477, and the nextlocation for resources to be added to the ImpactedResList is updated,STEP 1478. Processing then proceeds to STEP 1472.

When all pairings have been evaluated, iqprep is incremented, STEP 1479,and processing continues with INQUIRY 1469. When all perpetratingresources have been identified, the CR parings used is updated, STEP1480 (FIG. 14I), and the CR is updated in the CR table, STEP 1481.

The final phase of processing for AsynchQueryBuild forms messages to besent to the centralized focal point for gathering resource data on asystem image basis. An index is set to the beginning of theImpactedResList to step through the resource entries in the array, STEP1482. When the last resource has been processed, INQUIRY 1483,AsynchQueryBuild has completed. Otherwise, for the indexed resource inthe ImpactedResList, a determination is made if it has already beenprocessed, i.e., has this resource already been included in a requestfor data message, INQUIRY 1484. If so, the next resource in theImpactedResList is selected, STEP 1485.

For each resource in the ImpactedResList which has not already beenprocessed, INQUIRY 1484, an in-memory list of resources for which datais being requested, BRAD_List, is set to null, STEP 1486, and thenupdated with the resource from the ImpactedResList, STEP 1487. Further,the entry in the ImpactedResList is marked as processed, STEP 1488.

For every subsequent resource in the ImpactedResList, an index isestablished, STEP 1489 (FIG. 14J), and each remaining array entry isprocessed. For each remaining ImpactedResList array entry, if theresource is not on the same system as the seed resource placed in theBRAD_List, INQUIRY 1490, the entry is skipped and the next entryselected for evaluation, STEP 1493. For those resources on the samesystem, INQUIRY 1490, the resource is added to the BRAD_List ofresources for which resource data is being requested, STEP 1491, theassociated ImpactedResList entry is marked as processed, STEP 1492, andthe index is incremented, STEP 1493.

When all resources in the ImpactedResList have been evaluated, STEP1489, a determination is made if the mechanism for retrieving data forresources has been established, INQUIRY 1494. If not, the system hostingthe BRM is selected as the target for the resource data request message,STEP 1495. Thereafter, or if the mechanism has been established, a statequery for resource data is initiated to the mechanism for requestingresource data, STEP 1496, and the requested target is saved for laterprocessing when the response message is received, STEP 1497. Finally thenext entry in the ImpactedResList is indexed for evaluation, STEP 1485(FIG. 14I).

Close Sliding Window

The interval timer for expiration of the T3 interval gives control tothe CloseSlidingWindow routine. The T3 time interval from the firstevent notification causing creation of the CR represents the latestpoint in time where responses to asynchronous query build requests forresource state and property/value data can be accepted. The T3 timeinterval may be established in a variety of ways including fixedintervals provided within the product offering, fixed intervals definedby the customer or variable intervals. The CR progress is updated toreflect processing being in the T3 T4 phase. All subsequent responsesreceived in response to asynchronous query build requests are discarded.If responses to all queries for resource status subsequent to the mostrecent event notification related to the CR have not been received,control is passed to processing which substitutes cached resource stateand property values for missing resource status responses. Otherwise,control is passed to processing to formulate the recovery process.

One embodiment of the logic associated with the close sliding windowroutine is described with reference to FIG. 15. In one example, thislogic is performed by the BRM. Referring to FIG. 15, the CR associatedwith the ending T3 interval is retrieved with serialization, STEP 1500.If the CR.Progress reflects T2→T3 processing and theCr.MostCurrentEventTod is equal the CRQBTOD representing queryprocessing for the most current event associated with the CR, INQUIRY1502, processing continues. Otherwise, this routine terminates as the CRhas been merged or is already being processed.

In continuing, the CR.Progress is updated to reflect phase T3→T4processing, in process of building a recovery process, STEP 1504, andrecorded with serialization continued to be held by this process, STEP1506. Each BRAD_List entry associated with the CR is examined todetermine if a response to the latest AsynchQueryBuild request wasreceived, STEP 1508. When all CR.BRAD_List entries have been processed,the formation of a recovery process is initiated with resource state andproperty/values provided as input in the CR, STEP 1510.

For each entry, if the CRQBTOD of the BRAD_List entry being processedmatches the CR.MostCurrentEventTOD, INQUIRY 1512, a response to thelatest asynchronous query build request was received and currentresource state and property/values were retrieved. Thus, processingreturns to STEP 1508. Otherwise, for each resource in the CR, STEP 1514,a determination is made as to whether that resource is associated withthe BRAD which failed to provide a most current response, INQUIRY 1516.If not, processing continues to STEP 1514. Otherwise, for suchresources, the cached data for state, aggregated state andproperty/value data is filled into the CR.States array, STEP 1518.Processing then continues to STEP 1514. This concludes the close windowprocessing.

Related Processing

Calculate Interval Windows and/or associated processing may be invokedduring related BR processing. For example, in a routine,AssociateWithExistingCR, in which processing is performed, on eventnotification, to combine two or more CR(s), CalculateIntervalWindows isinvoked to recalculate the T2 and T3 intervals. Processing on return isthe same as on establishing T2 and T3 intervals when creating a new CR.

Additionally, when a CR has completed processing due to being subsumedby another CR, processing to cancel the T2 and T3 interval timers isperformed. If processing has not been initiated to retrieve resourcestate, there are no outstanding responses to be processed. If processingto retrieve resource state has been initiated, response messages may bein the process of being created and returned. When received, responsemessages identify the CR and the event for which the resource status wasrequested. If the CR has been subsumed, processing detects that theresponse is not needed and the response is discarded.

Described in detail herein is a capability for managing an ITenvironment that is facilitated by employing dynamically adjusteddiscrete phases or processing to obtain a set of event relatedinformation used in managing the environment.

One or more aspects of the present invention can be included in anarticle of manufacture (e.g., one or more computer program products)having, for instance, computer usable media. The media has therein, forinstance, computer readable program code means or logic (e.g.,instructions, code, commands, etc.) to provide and facilitate thecapabilities of the present invention. The article of manufacture can beincluded as a part of a computer system or sold separately.

One example of an article of manufacture or a computer program productincorporating one or more aspects of the present invention is describedwith reference to FIG. 16. A computer program product 1600 includes, forinstance, one or more computer usable media 1602 to store computerreadable program code means or logic 1604 thereon to provide andfacilitate one or more aspects of the present invention. The medium canbe an electronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system (or apparatus or device) or a propagation medium.Examples of a computer readable medium include a semiconductor or solidstate memory, magnetic tape, a removable computer diskette, a randomaccess memory (RAM), a read-only memory (ROM), a rigid magnetic disk andan optical disk. Examples of optical disks include compact disk-readonly memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.

A sequence of program instructions or a logical assembly of one or moreinterrelated modules defined by one or more computer readable programcode means or logic direct the performance of one or more aspects of thepresent invention.

Advantageously, a capability is provided for formalizing discrete phasesof processing to wait to initiate gathering of state information, tohave a point in time in which a query to obtain current stateinformation is initiated, to formalize the period of time for takingaction, such as building a recovery process, and to take action (e.g.,execute the recovery process). Advantageously, the points in time areadjustable based on real-time events that are reported or detectedthrough status queries. The event may be related to availability, or toother types of events (e.g., dispatching, configuration changes, etc.),as examples. Advantageously, the amount of time to wait to obtain a setof related events is dynamically adjustable.

Although various embodiments are described above, these are onlyexamples. For example, the processing environments described herein areonly examples of environments that may incorporate and use one or moreaspects of the present invention. Environments may include other typesof processing units or servers or the components in each processingenvironment may be different than described herein. Each processingenvironment may include additional, less and/or different componentsthan described herein. Further, the types of central processing unitsand/or operating systems or other types of components may be differentthan described herein. Again, these are only provided as examples.

Moreover, an environment may include an emulator (e.g., software orother emulation mechanisms), in which a particular architecture orsubset thereof is emulated. In such an environment, one or moreemulation functions of the emulator can implement one or more aspects ofthe present invention, even though a computer executing the emulator mayhave a different architecture than the capabilities being emulated. Asone example, in emulation mode, the specific instruction or operationbeing emulated is decoded, and an appropriate emulation function isbuilt to implement the individual instruction or operation.

In an emulation environment, a host computer includes, for instance, amemory to store instructions and data; an instruction fetch unit toobtain instructions from memory and to optionally, provide localbuffering for the obtained instruction; an instruction decode unit toreceive the instruction fetched and to determine the type ofinstructions that have been fetched; and an instruction execution unitto execute the instructions. Execution may include loading data into aregister for memory; storing data back to memory from a register; orperforming some type of arithmetic or logical operation, as determinedby the decode unit. In one example, each unit is implemented insoftware. For instance, the operations being performed by the units areimplemented as one or more subroutines within emulator software.

Further, a data processing system suitable for storing and/or executingprogram code is usable that includes at least one processor coupleddirectly or indirectly to memory elements through a system bus. Thememory elements include, for instance, local memory employed duringactual execution of the program code, bulk storage, and cache memorywhich provide temporary storage of at least some program code in orderto reduce the number of times code must be retrieved from bulk storageduring execution.

Input/Output or I/O devices (including, but not limited to, keyboards,displays, pointing devices, DASD, tape, CDs, DVDs, thumb drives andother memory media, etc.) can be coupled to the system either directlyor through intervening I/O controllers. Network adapters may also becoupled to the system to enable the data processing system to becomecoupled to other data processing systems or remote printers or storagedevices through intervening private or public networks. Modems, cablemodems, and Ethernet cards are just a few of the available types ofnetwork adapters.

Further, although the environments described herein are related to themanagement of availability of a customer's environment, one or moreaspects of the present invention may be used to manage aspects otherthan or in addition to availability. Further, one or more aspects of thepresent invention can be used in environments other than a businessresiliency environment.

Yet further, many examples are provided herein, and these examples maybe revised without departing from the spirit of the present invention.For example, in one embodiment, the description is described in terms ofavailability and recovery; however, other goals and/or objectives may bespecified in lieu of or in addition thereto. Additionally, the resourcesmay be other than IT resources. Further, there may be references toparticular products offered by International Business MachinesCorporation or other companies. These again are only offered asexamples, and other products may also be used. Additionally, althoughtables and databases are described herein, any suitable data structuremay be used. There are many other variations that can be included in thedescription described herein and all of these variations are considereda part of the claimed invention.

Further, for completeness in describing one example of an environment inwhich one or more aspects of the present invention may be utilized,certain components and/or information is described that is not neededfor one or more aspects of the present invention. These are not meant tolimit the aspects of the present invention in any way.

One or more aspects of the present invention can be provided, offered,deployed, managed, serviced, etc. by a service provider who offersmanagement of customer environments. For instance, the service providercan create, maintain, support, etc. computer code and/or a computerinfrastructure that performs one or more aspects of the presentinvention for one or more customers. In return, the service provider canreceive payment from the customer under a subscription and/or feeagreement, as examples. Additionally or alternatively, the serviceprovider can receive payment from the sale of advertising content to oneor more third parties.

In one aspect of the present invention, an application can be deployedfor performing one or more aspects of the present invention. As oneexample, the deploying of an application comprises providing computerinfrastructure operable to perform one or more aspects of the presentinvention.

As a further aspect of the present invention, a computing infrastructurecan be deployed comprising integrating computer readable code into acomputing system, in which the code in combination with the computingsystem is capable of performing one or more aspects of the presentinvention.

As yet a further aspect of the present invention, a process forintegrating computing infrastructure, comprising integrating computerreadable code into a computer system may be provided. The computersystem comprises a computer usable medium, in which the computer usablemedium comprises one or more aspects of the present invention. The codein combination with the computer system is capable of performing one ormore aspects of the present invention.

The capabilities of one or more aspects of the present invention can beimplemented in software, firmware, hardware, or some combinationthereof. At least one program storage device readable by a machineembodying at least one program of instructions executable by the machineto perform the capabilities of the present invention can be provided.

The flow diagrams depicted herein are just examples. There may be manyvariations to these diagrams or the steps (or operations) describedtherein without departing from the spirit of the invention. Forinstance, the steps may be performed in a differing order, or steps maybe added, deleted, or modified. All of these variations are considered apart of the claimed invention.

Although embodiments have been depicted and described in detail herein,it will be apparent to those skilled in the relevant art that variousmodifications, additions, substitutions and the like can be made withoutdeparting from the spirit of the invention and these are thereforeconsidered to be within the scope of the invention as defined in thefollowing claims.

1. A computer-implemented method to facilitate event correlation, saidmethod comprising: executing a plurality of discrete phases ofprocessing, in response to an occurrence of an event in an InformationTechnology (IT) environment, to obtain a set of related informationassociated with the event; and adjusting a time interval associated withat least one discrete phase of the plurality of discrete phases based onreal-time status of the IT environment, said adjusting affecting theobtained set of related information.
 2. The computer-implemented methodof claim 1, further comprising using the obtained set of relatedinformation to manage the IT environment.
 3. The computer-implementedmethod of claim 2, wherein the obtained set of related information isused to manage availability of the IT environment.
 4. Thecomputer-implemented method of claim 3, wherein availability of the ITenvironment is managed within a specified goal.
 5. Thecomputer-implemented method of claim 4, wherein the specified goalcomprises a recovery time objective.
 6. The computer-implemented methodof claim 5, wherein the recovery time objective is related to a businessapplication of the IT environment.
 7. The computer-implemented method ofclaim 1, wherein the plurality of discrete phases comprises firstoccurrence of the event, time from first occurrence of the event to atime to start collecting state information, time to stop collecting thestate information, time to formulate an action plan for the one or moreevents, projected time to end taking action.
 8. The computer-implementedmethod of claim 7, wherein the projected time to end is prior to a goalobjective of one or more resources affected by the event.
 9. Thecomputer-implemented method of claim 1, wherein the adjusting provides adelay to enable additional information relating to the event to beincluded in the set of related information.
 10. The computer-implementedmethod of claim 1, wherein one or more relationships are used to obtainthe set of related information.
 11. The computer-implemented method ofclaim 10, wherein the relationships comprise at least one of one or moreimplied relationships or one or more explicit relationships.
 12. Thecomputer-implemented method of claim 1, wherein time to complete eachdiscrete phase is determined at runtime.
 13. The computer-implementedmethod of claim 1, wherein the time for each discrete phase isdynamically calculated to achieve a goal specified for the ITenvironment.
 14. The computer-implemented method of claim 1, wherein theevent comprises occurrence of a plurality of correlated failures.
 15. Asystem to facilitate event correlation, said system comprising: at leastone processor to execute a plurality of discrete phases of processing,in response to an occurrence of an event in an Information Technology(IT) environment, to obtain a set of related information associated withthe event; and at least one processor to adjust a time intervalassociated with at least one discrete phase of the plurality of discretephases based on real-time status of the IT environment, said adjustingaffecting the obtained set of related information.
 16. The system ofclaim 15, wherein the obtained set of related information is used tomanage availability of the IT environment within a specified goal. 17.The system of claim 15, wherein one or more relationships are used toobtain the set of related information.
 18. An article of manufacturecomprising: at least one computer usable medium having computer readableprogram code logic to facilitate event correlation, said computerreadable program code logic when executing performing the following:executing a plurality of discrete phases of processing, in response toan occurrence of an event in an Information Technology (IT) environment,to obtain a set of related information associated with the event; andadjusting a time interval associated with at least one discrete phase ofthe plurality of discrete phases based on real-time status of the ITenvironment, said adjusting affecting the obtained set of relatedinformation.
 19. The article of manufacture of claim 18, furthercomprising using the obtained set of related information to manageavailability of the IT environment within a specified goal.
 20. Thearticle of manufacture of claim 18, wherein the adjusting provides adelay to enable additional information relating to the event to beincluded in the set of related information.